Building system with user presentation composition based on building context

ABSTRACT

A building system includes one or more storage devices having instructions stored thereon that, when executed by one or more processors, cause the one or more processors to receive an unstructured user question from a user device of a user and query a graph database based on the unstructured user question to extract context associated with the unstructured user question from contextual information of a building stored by the graph database, wherein the graph database stores the contextual information of the building through nodes and edges between the nodes, wherein the nodes represent equipment, spaces, people, and events associated building and the edges represent relationships between the equipment, spaces, people, and events. The instructions further cause the one or more processors to retrieve data from one or more data sources based on the context and compose a presentation based on the retrieved data.

CROSS-REFERENCE TO RELATED PATENT APPLICATIONS

This application claims the benefit of and priority to U.S. ProvisionalPatent Application No. 62/951,892 filed Dec. 20, 2019 and U.S.Provisional Patent Application No. 62/929,610 filed Nov. 1, 2019. Thisapplication is also a continuation-in-part of U.S. patent applicationSer. No. 16/008,885 filed Jun. 14, 2018 which claims the benefit of andpriority to U.S. Provisional Patent Application No. 62/520,380 filedJun. 15, 2017. This application is also a continuation-in-part of U.S.patent application Ser. No. 16/014,936 filed Jun. 21, 2018 which claimsthe benefit of and priority to U.S. Provisional Patent Application No.62/523,211 filed Jun. 21, 2017. U.S. patent application Ser. No.16/014,936 filed Jun. 21, 2018 is also a continuation-in-part of U.S.patent application Ser. No. 15/586,104 filed May 3, 2017 which claimsthe benefit of and priority to U.S. Provisional Patent Application No.62/331,888 filed May 4, 2016. U.S. patent application Ser. No.15/586,104 filed May 3, 2017 is a continuation of U.S. patentapplication Ser. No. 15/367,167 filed Dec. 1, 2016 which claims thebenefit of U.S. Provisional Patent Application No. 62/360,935 filed Jul.11, 2016. This application is also a continuation-in-part of U.S. patentapplication Ser. No. 16/688,819 filed Nov. 19, 2019 which is acontinuation of U.S. patent application Ser. No. 16/260,078 filed Jan.28, 2019 which is a continuation-in-part of U.S. patent application Ser.No. 16/048,052 filed Jul. 27, 2018 which claims the benefit of andpriority to U.S. Provisional Patent Application No. 62/564,247 filedSep. 27, 2017, U.S. Provisional Patent Application No. 62/611,974 filedDec. 29, 2017, and U.S. Provisional Patent Application No. 62/611,984filed Dec. 29, 2017. The entirety of each of these patent applicationsis incorporated by referenced herein.

BACKGROUND

The present disclosure relates generally to building management systems.The present disclosure relates more particularly to data analytics andinformation presentation of the building management system.

Many building management systems include a user interface application.The user interface application is run on top of data analyticsalgorithms that generate data for presentation in the user interfaceapplication. Both the user interface application and the data analyticsare designed by a developer. Once deployed, the one or more dataanalytics and the user interface application operate in a static,predefined manner until they are updated by the developer. The dataanalytics and user interface applications meet a design goal instead ofdynamically meeting the needs or preferences of a user who may beinteracting with the user interface application. More specifically, theuser interface application only presents the information that thedeveloper has designed it to present, the user interface applicationcannot, by itself, change based on the interest of the user, contextualinformation describing the user, or context information describing abuilding.

SUMMARY

One implementation of the present disclosure is a building systemincluding one or more storage devices having instructions stored thereonthat, when executed by one or more processors, cause the one or moreprocessors to receive an unstructured user question from a user deviceof a user and query a graph database based on the unstructured userquestion to extract context associated with the unstructured userquestion from contextual information of a building stored by the graphdatabase, wherein the graph database stores the contextual informationof the building through a plurality of nodes and a plurality of edgesbetween the plurality of nodes, wherein the plurality of nodes representbuilding entities of the building and the plurality of edges representrelationships between the building entities. The instructions cause theone or more processors to retrieve building data from one or more datasources based on the context and compose a presentation based on thebuilding data.

Another implementation of the present disclosure is a building systemincluding one or more storage devices having instructions stored thereonthat, when executed by one or more processors, cause the one or moreprocessors to receive an unstructured user question from a user deviceof a user, query a graph database based on the unstructured userquestion to extract context associated with the unstructured userquestion from contextual information of a building stored by the graphdatabase, wherein the graph database stores the contextual informationof the building through a plurality of nodes and a plurality of edgesbetween the plurality of nodes, wherein the plurality of nodes representequipment, spaces, people, and events associated with the building andthe plurality of edges represent relationships between the equipment,spaces, people, and events, wherein the one or more processors areconfigured to extract the context for multiple portions of theunstructured user question across two or more of the equipment, spaces,people, or events. The instructions cause the one or more processors toretrieve data from one or more data sources based on the context togenerate a response to the user question and compose a presentationbased on the retrieved data.

In some embodiments, the one or more data sources are one or moreparticular nodes of the graph database.

In some embodiments, the instructions cause the one or more processorsto implement a data ingestion service configured to collect the datafrom an edge device of the building and ingest the data into the graphdatabase, the graph database, wherein the graph database is configuredto store the data, and a dynamic user experience service configured toreceive the unstructured user question, query the graph database, andcompose the presentation.

In some embodiments, the unstructured user question is a string. In someembodiments, the instructions cause the one or more processors todecompose the string to determine a requested information context and apresentation context based on the string, query the graph database forthe data of the building based on the requested information context, andcompose the presentation based on the data and the presentation contextby determining a format of the presentation based on the presentationcontext.

In some embodiments, the plurality of nodes represent the building data.

In some embodiments, the unstructured user question is a stringincluding an identifier of an edge device associated with the data andan indication of a type of the data. In some embodiments, theinstructions cause the one or more processors to decompose the string todetermine a first component and a second component of the string,wherein the first component is the identifier of the edge deviceassociated with the data and the second component is the type of thedata, query the graph database for the building data of the buildingwith the first component and the second component.

In some embodiments, the unstructured user question is a stringincluding an indication of a requested output presentation, wherein therequested output presentation is at least one of a visual outputpresentation, a textual output presentation, or an audible outputpresentation. In some embodiments, the instructions cause the one ormore processors to decompose the string to determine a component of thestring, wherein the component is the indication of the requested outputpresentation and compose the presentation based on the component of thestring by determining whether the component indicates the visual outputpresentation, the textual output presentation, or the audible outputpresentation, composing the presentation as the visual outputpresentation in response to a first determination that the componentindicates the visual output presentation, composing the presentation asthe text output presentation in response to a second determination thatthe component indicates the text output presentation, and composing thepresentation as the audible output presentation in response to a thirddetermination that the component indicates the audible outputpresentation.

In some embodiments, the instructions cause the one or more processorsto query the graph database for at least a portion of the data and acontext portion of the contextual information describing the building,perform one or more analytic algorithms based on the portion of the dataand the context portion of the contextual information to generate one ormore analytics results, and push the one or more analytics results tothe user device of the user.

In some embodiments, the instructions cause the one or more processorsto retrieve at least one of historical question data associated with theuser or user contextual data describing the user and select the one ormore analytic algorithms from a plurality of analytic algorithms basedon at least one of the historical question data associated with the useror the user contextual data describing the user.

In some embodiments, the unstructured user question is a string. In someembodiments, the instructions cause the one or more processors todecompose the string to determine a requested information context and apresentation context, query the graph database for the context based onthe requested information context, generate a query data structure basedon the context, query the graph database based on the query datastructure for the data of the building, and compose the presentationbased on the data and the presentation context.

In some embodiments, the requested information context includes arequest for one or more actions associated with the user of the userdevice, wherein the requested information context further includes anindication of the user.

In some embodiments, the context includes at least one of one or moreparticular nodes of the graph database or one or more particular edgesof the graph database. In some embodiments, the instructions cause theone or more processors to generate the query data structure by causingthe query data structure to include one or more parameters based on atleast one of the one or more particular nodes of the graph database orthe one or more particular edges of the graph database.

In some embodiments, the instructions cause the one or more processorsto receive an indication of the data being ingested into the graphdatabase, determine, based on the data, that a presentation rule of aplurality of presentation rules is triggered based on the data, querythe graph database based on the presentation rule and the data toidentify the user, compose a second presentation based on the data andthe presentation rule, and push the second presentation to the userdevice of the user.

In some embodiments, the instructions cause the one or more processorsto retrieve historical question data based on an identity of the user,identify one or more presentation preferences of the user based on thehistorical question data, and compose the second presentation based onthe data, the presentation rule, and the one or more presentationpreferences.

In some embodiments, the instructions cause the one or more processorsto compose the second presentation based on the data and thepresentation rule by selecting one presentation template from aplurality of presentation templates based on the data and thepresentation rule, wherein each of the plurality of presentationtemplates defines a presentation format and composing the secondpresentation based on the data and the one presentation template.

Another implementation of the present disclosure is a method includingreceiving, by a processing circuit, an unstructured user question from auser device of a user, querying, by the processing circuit, a graphdatabase based on the unstructured user question to extract contextassociated with the unstructured user question from contextualinformation of a building stored by the graph database, wherein thegraph database stores the contextual information of the building througha plurality of nodes and a plurality of edges between the plurality ofnodes, wherein the plurality of nodes represent building entities of thebuilding and the plurality of edges represent relationships between thebuilding entities, retrieving, by the processing circuit, building datafrom one or more data sources based on the context, and composing, bythe processing circuit, a presentation based on the building data.

Another implementation of the present disclosure is a method includingreceiving, by a processing circuit, an unstructured user question from auser device of a user and querying, by the processing circuit, adatabase based on the unstructured user question to extract contextassociated with the unstructured user question from contextualinformation of a building stored by the database, wherein the databasestores the contextual information of the building through a plurality ofnodes and a plurality of edges between the plurality of nodes, whereinthe plurality of nodes represent equipment, spaces, people, and eventsassociated with the building and the plurality of edges representrelationships between the equipment, spaces, people, and events, whereinthe querying includes extracting the context for multiple portions ofthe unstructured user question across two or more of the equipment,spaces, people, or events. The method further includes retrieving, bythe processing circuit, data from one or more data sources based on thecontext to generate a response to the user question and composing, bythe processing circuit, a presentation based on the retrieved data.

In some embodiments, the unstructured user question is a string. In someembodiments, the method further includes decomposing, by the processingcircuit, the string to determine a requested information context and apresentation context based on the string, querying, by the processingcircuit, the database for the data of the building based on therequested information context, and composing, by the processing circuit,the presentation based on the data and the presentation context bydetermining a format of the presentation based on the presentationcontext.

In some embodiments, the plurality of nodes represent the data.

In some embodiments, the database is a graph database. In someembodiments, the one or more data sources are one or more particularnodes of the graph database.

In some embodiments, the unstructured user question is a stringincluding an identifier of an edge device associated with the data andan indication of a type of the data. In some embodiments, the methodfurther includes decomposing, by the processing circuit, the string todetermine a first component and a second component of the string,wherein the first component is the identifier of the edge deviceassociated with the data and the second component is the type of thedata and querying, by the processing circuit, the database for the dataof the building with the first component and the second component.

In some embodiments, the unstructured user question is a stringincluding an indication of a requested output presentation, wherein therequested output presentation is at least one of a visual outputpresentation, a textual output presentation, or an audible outputpresentation. In some embodiments, the method further includesdecomposing, by the processing circuit, the string to determine acomponent of the string, wherein the component is the indication of therequested output presentation and composing, by the processing circuit,the presentation based on the component of the string by determiningwhether the component indicates the visual output presentation, thetextual output presentation, or the audible output presentation,composing the presentation as the visual output presentation in responseto a first determination that the component indicates the visual outputpresentation, composing the presentation as the text output presentationin response to a second determination that the component indicates thetext output presentation, and composing the presentation as the audibleoutput presentation in response to a third determination that thecomponent indicates the audible output presentation.

In some embodiments, the method further includes querying, by theprocessing circuit, the database for at least a portion of the data anda context portion of the contextual information describing the building,performing, by the processing circuit, one or more analytic algorithmsbased on the portion of the data and the context portion of thecontextual information to generate one or more analytics results, andpushing, by the processing circuit, the one or more analytics results tothe user device of the user.

In some embodiments, the method further includes retrieving, by theprocessing circuit, at least one of historical question data associatedwith the user or user contextual data describing the user and selecting,by the processing circuit, the one or more analytic algorithms from aplurality of analytic algorithms based on at least one of the historicalquestion data associated with the user or the user contextual datadescribing the user.

In some embodiments, the unstructured user question is a string. In someembodiments, the method further includes decomposing, by the processingcircuit, the string to determine a requested information context and apresentation context, querying, by the processing circuit, the databasefor the context based on the requested information context, generating,by the processing circuit, a query data structure based on the context,querying, by the processing circuit, the database based on the querydata structure for the data of the building, and composing, by theprocessing circuit, the presentation based on the data and thepresentation context.

In some embodiments, the requested information context includes arequest for one or more actions associated with the user of the userdevice, wherein the requested information context further includes anindication of the user.

In some embodiments, the context includes at least one of one or moreparticular nodes of the database or one or more particular edges of thedatabase. In some embodiments, the method further includes generating,by the processing circuit, the query data structure by causing the querydata structure to include one or more parameters based on at least oneof the one or more particular nodes of the database or the one or moreparticular edges of the database.

In some embodiments, the method further includes receiving, by theprocessing circuit, an indication of the data being ingested into thedatabase, determining, by the processing circuit, based on the data,that a presentation rule of a plurality of presentation rules istriggered based on the data, querying, by the processing circuit, thedatabase based on the presentation rule and the data to identify theuser, composing, by the processing circuit, a second presentation basedon the data and the presentation rule, and pushing, by the processingcircuit, the second presentation to the user device of the user.

In some embodiments, the method includes retrieving, by the processingcircuit, historical question data based on an identity of the user,identifying, by the processing circuit, one or more presentationpreferences of the user based on the historical question data, andcomposing, by the processing circuit, the second presentation based onthe data, the presentation rule, and the one or more presentationpreferences.

In some embodiments, the method includes composing, by the processingcircuit, the second presentation based on the data and the presentationrule includes selecting one presentation template from a plurality ofpresentation templates based on the data and the presentation rule,wherein each of the plurality of presentation templates defines apresentation format and composing the second presentation based on thedata and the one presentation template.

Another implementation of the present disclosure is a buildingmanagement system of a building including one or more storage devicesconfigured to store instructions and store a knowledgebase includingcontextual information of the building, wherein the contextualinformation includes representations of equipment, spaces, people, andevents associated with the building and relationships between theequipment, spaces, people, and events. The system includes one or moreprocessing circuits configured to execute the instructions causing theone or more processing circuits to receive an unstructured user questionfrom a user device of a user, query the knowledgebase based on theunstructured user question to extract context associated with theunstructured user question from the contextual information of thebuilding stored by the knowledgebase, wherein the one or more processorsare configured to extract the context for multiple portions of theunstructured user question across two or more of the equipment, spaces,people, or events, retrieve data from the knowledgebase based on thecontext to generate a response to the user question, and compose apresentation based on the retrieved data.

Another implementation of the present disclosure is a buildingmanagement system a building including one or more storage devicesconfigured to store instructions and store a knowledgebase includingcontextual information of the building, wherein the contextualinformation includes representations of building entities of thebuilding and relationships between the building entities and one or moreprocessing circuits. The one or more processing circuits are configuredto execute the instructions causing the one or more processing circuitsto receive an unstructured user question from a user device of a user,query the knowledgebase based on the unstructured user question toextract context associated with the unstructured user question from thecontextual information of the building stored by the knowledgebase,retrieve building data from the knowledgebase based on the context, andcompose a presentation based on the building data.

In some embodiments, the knowledgebase is a graph database including aplurality of nodes representing the building entities and a plurality ofedges between the plurality of nodes representing the relationships. Insome embodiments, the plurality of nodes represent equipment, spaces ofthe building, people, and the building data.

In some embodiments, the knowledgebase is a digital twin that provides avirtual representation of the equipment, spaces, people, and eventsassociated with the building.

Pull—Responding to User Questions By Querying A Knowledgebase Based OnUser Input

One implementation of the present disclosure is a building managementsystem of a building including one or more memory devices configured tostore instructions thereon, that, when executed by the one or moreprocessing circuits, cause the one or more processing circuits toimplement a data ingestion service configured to collect building datafrom an edge device of the building and ingest the building data into aknowledgebase. The instructions further cause the one or more processingcircuits to implement the knowledgebase, wherein the knowledgebase isconfigured to store the building data. The instructions further causethe one or more processing circuits to implement an dynamic userexperience service configured to receive user input from a user device,wherein the user input is a string, decompose the string to determine arequested information context and a presentation context based on thestring, query the knowledgebase for the building data of the buildingbased on the requested information context, and compose a presentationbased on the building data and the presentation context, wherein thedynamic user experience service determines a format of the presentationbased on the presentation context.

In some embodiments, the knowledgebase is a graph data structureincluding nodes and edges. In some embodiments, the nodes representequipment, spaces of the building, people, and the building data. Insome embodiments, the edges represent relationships between at leastsome of the equipment, the spaces of the building, the people, and thebuilding data.

In some embodiments, the string includes an identifier of the edgedevice and an indication of a type of the building data. In someembodiments, the dynamic user experience service is configured todecompose the string to determine a first component and a secondcomponent of the string, wherein the first component is the identifierof the edge device and the second component is the type of the buildingdata query the knowledgebase for the building data of the building withthe first component and the second component.

In some embodiments, the dynamic user experience service is configuredto receive a second user input from the user device, wherein the seconduser input is a second string, decompose the second user input todetermine follow-on context for a question associated with thepresentation and a second presentation context, and compose a secondpresentation based on the building data, the follow-on context, and thesecond presentation context, wherein the dynamic user experience servicedetermines a second format of the second presentation based on thesecond presentation context.

In some embodiments, the string includes an indication of a requestedoutput presentation, wherein the output presentation is at least one ofa request for a visual output presentation or a request for a textoutput presentation. In some embodiments, the dynamic user experienceservice is configured to decompose the string to determine a componentof the string, wherein the component is the indication of the requestedoutput presentation, compose the presentation based on the component ofthe string by determining whether the component is the request for thevisual output presentation or the request for the text outputpresentation, compose the presentation as a visual output presentationin response to a determination that the component is the request for thevisual output presentation, and compose the presentation as a textoutput presentation in response to a determination that the component isthe request for the text output presentation.

In some embodiments, the dynamic user experience service furthercomposes the presentation by generating an audio output based on thetext output presentation.

Pull—Responding to User Questions By Generating Contextual BuildingQueries For A Building Knowledgebase

One implementation of the present disclosure is a building managementsystem of a building including one or more memory devices configured tostore instructions thereon, that, when executed by the one or moreprocessing circuits, cause the one or more processing circuits toimplement a data ingestion service configured to collect building datafrom an edge device of the building and ingest the building data into aknowledgebase. The instructions cause the one or more processingcircuits to implement the knowledgebase, wherein the knowledgebase isconfigured to store the building data and contextual informationdescribing the building. The instructions cause the one or moreprocessing circuits to implement an dynamic user experience serviceconfigured to receive user input from a user device, wherein the userinput is a string, decompose the string to determine a requestedinformation context and a presentation context, query the knowledgebasefor a portion of the contextual information of the building based on therequested information context, generate a query data structure based onthe portion of the contextual information, query the knowledgebase basedon the query data structure for the building data of the building, andcompose a presentation based on the building data and the presentationcontext.

In some embodiments, the requested information context includes arequest for one or more actions associated with a user of the userdevice, wherein the requested information context further includes anindication of the user.

In some embodiments, the string includes an indication of a requestedoutput presentation, wherein the output presentation is at least one ofa request for a visual output presentation or a request for a textoutput presentation. In some embodiments, the dynamic user experienceservice is configured to decompose the string to determine a componentof the string, wherein the component is the indication of the requestedoutput presentation and compose the presentation based on the componentof the string by determining whether the component is the request forthe visual output presentation or the request for the text outputpresentation, compose the presentation as a visual output presentationin response to a determination that the component is the request for thevisual output presentation, and compose the presentation as a textoutput presentation in response to a determination that the component isthe request for the text output presentation.

In some embodiments, the knowledgebase is a graph data structureincluding nodes and edges. In some embodiments, the nodes representequipment, spaces of the building, people, and the building data. Insome embodiments, the edges represent relationships between at leastsome of the equipment, the spaces of the building, the people, and thebuilding data.

In some embodiments, the portion of the contextual information includesat least one of one or more particular nodes of the graph data structureor one or more particular edges of the graph data structure. In someembodiments, the dynamic user experience service is configured togenerate the query data structure by causing the query data structure toinclude one or more parameters based on at least one of the one or moreparticular nodes or the one or more particular edges.

In some embodiments, the query data structure includes a first parameterassociated with the building data to return for the query data structureand a second parameter associated with second data to return for thequery data structure. In some embodiments, the dynamic user experienceservice is configured to query the knowledgebase based on the query datastructure for the building data and the second data and compose thepresentation based on the building data, the second data, and thepresentation context.

In some embodiments, the second data is contextual user data describinga user of the user device.

Push—Triggering Presentation To A User

Another implementation of the present application is a buildingmanagement system of a building including one or more memory devicesconfigured to store instructions thereon, that, when executed by the oneor more processing circuits, cause the one or more processing circuitsto implement a data ingestion service configured to collect buildingdata from an edge device of the building and ingest the building datainto a knowledgebase. The instructions cause the one or more processingcircuits to implement the knowledgebase, wherein the knowledgebase isconfigured to store the building data and contextual informationdescribing the building. The instructions cause the one or moreprocessing circuits to implement a dynamic user experience serviceconfigured to receive an indication of the building data being ingestedinto the knowledgebase, determine, based on the building data, that apresentation rule of presentation rules is triggered based on thebuilding data, query the knowledgebase based on the presentation ruleand the building data to identify a user, compose a presentation basedon the building data and the presentation rule, and push thepresentation to a user device of the user.

In some embodiments, the dynamic user experience service is configuredto retrieve historical question data based on an identity of the user,identify on or more presentation preferences of the user based on thehistorical question data, and compose the presentation based on thebuilding data, the presentation rule, and the presentation preferences.

In some embodiments, the knowledgebase is a graph data structureincluding nodes and edges. In some embodiments, the nodes representequipment, spaces of the building, people, and the building data. Insome embodiments, the edges represent relationships between at leastsome of the equipment, the spaces of the building, the people, and thebuilding data.

In some embodiments, the dynamic user experience service is configuredto compose the presentation based on the building data and thepresentation rule by selecting one presentation template frompresentation templates based on the building data and the presentationrule, wherein each of the presentation templates defines a presentationformat and composing the presentation based on the building data and theone presentation template.

In some embodiments, the dynamic user experience service is configuredto receive a user input from the user device, wherein the user input isa string, decompose user input to determine a follow-on context for aquestion associated with the presentation and a second presentationcontext, and compose a second presentation based on the building data,the follow-on context, and the second presentation context, wherein thedynamic user experience service determines a format of the secondpresentation based on the second presentation context.

In some embodiments, the dynamic user experience service is configuredto query the knowledgebase for at least a portion of the building dataand a portion of the contextual information describing the building,perform one or more analytic algorithms based on the portion of thebuilding data and the portion of the contextual information to generateone or more analytics results, and push the one or more analyticsresults to the user device of the user.

In some embodiments, the dynamic user experience service is configuredto retrieve at least one of historical question data associate with theuser or user contextual data describing the user and select the one ormore analytic algorithms from analytic algorithms based on at least oneof the historical question data associated with the user or the usercontextual data describing the user.

In some embodiments, the one or more analytics results are associatedwith a building system. In some embodiments, the dynamic user experienceservice is configured to identify the user by querying the knowledgebasebased on the building system, wherein the user is linked to the buildingsystem by the knowledgebase.

In some embodiments, the dynamic user experience service is configuredto perform one or more analytic algorithms by operating a buildingequipment model of building equipment based on operating settings forthe building equipment, wherein the building equipment model providesresult data for each of the operating settings and selecting oneoperating setting of the operating settings based on the result data foreach of the operating settings, wherein the one or more analytic resultsinclude the one operating setting.

BRIEF DESCRIPTION OF THE DRAWINGS

Various objects, aspects, features, and advantages of the disclosurewill become more apparent and better understood by referring to thedetailed description taken in conjunction with the accompanyingdrawings, in which like reference characters identify correspondingelements throughout. In the drawings, like reference numbers generallyindicate identical, functionally similar, and/or structurally similarelements.

FIG. 1 is a block diagram of a UI-less UX system of a building includinga dynamic user experience (UX) service and a knowledgebase, where theUI-less UX system receives user questions from a user device of a userand composes responses for presentation to the user via the user device,according to an exemplary embodiment.

FIG. 2 is a block diagram of a question provided to the dynamic UXservice by the user device, the question asking to be shown faultinformation of a particular controller, according to an exemplaryembodiment.

FIG. 3 is a block diagram of a question provided to the dynamic UXservice by the user device, the question asking to be told the faultinformation of the particular controller, according to an exemplaryembodiment.

FIG. 4 is a graph data structure indicating building context of thebuilding, where the graph data structure is an example of theknowledgebase, according to an exemplary embodiment.

FIG. 5 is a block diagram of the dynamic UX service in greater detailillustrating the dynamic UX service processing the questions of FIGS.2-3 to compose a presentation for the user device, according to anexemplary embodiment.

FIG. 6 is the graph data structure of FIG. 4 illustrating nodes andedges of the graph data structure queried by the dynamic UX service toanswer the questions of FIGS. 2-3, according to an exemplary embodiment.

FIGS. 7-9 are examples of a conversation between the user via the userdevice and the dynamic UX service illustrating the question of FIG. 2and the response composed for the question of FIG. 2 by the dynamic UXservice, according to an exemplary embodiment.

FIGS. 10-12 are examples of a conversation between the user via the userdevice and the dynamic UX service illustrating the question of FIG. 3and the response composed for the question of FIG. 3 by the dynamic UXservice, according to an exemplary embodiment.

FIG. 13 is a block diagram of a question provided to the dynamic UXservice by the user device, the question asking to be shown faultinformation associated with the user, according to an exemplaryembodiment.

FIG. 14 is a graph data structure indicating building context of thebuilding, where the graph data structure is an example of theknowledgebase, according to an exemplary embodiment.

FIG. 15 is a block diagram of the dynamic UX service in greater detailillustrating the dynamic UX service processing the question of FIG. 14to generate a query data structure for querying the graph data structureof FIG. 14 and composing a presentation for the user device, accordingto an exemplary embodiment.

FIG. 16 is the graph data structure of FIG. 14 illustrating the graphdata structure being queried to generate the query data structure ofFIG. 15, according to an exemplary embodiment.

FIG. 17 is the query data structure of FIG. 15 generated based onquerying the graph data structure as shown in FIG. 16, according to anexemplary embodiment.

FIG. 18 is the graph data structure of FIG. 14 queried based on thequery data structure of FIG. 17 to retrieve fault data, according to anexemplary embodiment.

FIGS. 19-21 are examples of a conversation between the user via the userdevice and the dynamic UX service illustrating the question of FIG. 13and the response composed for the question of FIG. 13 by the dynamic UXservice, according to an exemplary embodiment.

FIG. 22 is a block diagram of a question provided to the dynamic UXservice by the user device, the question asking to be shown a list ofactions associated with the user to be completed before the user leavesthe building, according to an exemplary embodiment.

FIG. 23 is a graph data structure indicating building context of thebuilding, where the graph data structure is an example of theknowledgebase, according to an exemplary embodiment.

FIG. 24 is a block diagram of the dynamic UX service in greater detailillustrating the dynamic UX service processing the question of FIG. 23to generate a query data structure for querying the graph data structureof FIG. 23 and composing a presentation for the user device, accordingto an exemplary embodiment.

FIG. 25 is the graph data structure of FIG. 24 illustrating the graphdata structure being queried to generate the query data structure ofFIG. 24, according to an exemplary embodiment.

FIG. 26 is the query data structure of FIG. 24 generated based onquerying the graph data structure as shown in FIG. 25, according to anexemplary embodiment.

FIG. 27 is the graph data structure of FIG. 24 queried based on thequery data structure of FIG. 26 to retrieve fault data, according to anexemplary embodiment.

FIGS. 28-30 are examples of a conversation between the user via the userdevice and the dynamic UX service illustrating the question of FIG. 22and the response composed for the question of FIG. 22 by the dynamic UXservice, according to an exemplary embodiment.

FIG. 31 is a block diagram of the dynamic UX service, the knowledgebase,and the analytics engine service of FIG. 1 generating a nested faulttree for identification of a root fault for presentation to a user,according to an exemplary embodiment.

FIG. 32 is a block diagram of a graph data structure that the dynamic UXservice of FIG. 1 can query for information, the graph data structureincluding user roles, according to an exemplary embodiment.

FIG. 33 is a block diagram of a question frequency graph illustratinghow often users ask particular questions, according to an exemplaryembodiment.

DETAILED DESCRIPTION

Referring generally to the FIGURES, a building system with userpresentation composition based on building context is shown, accordingto various exemplary embodiments. The building system can be configuredto receive unstructured user questions, i.e., questions provided by theuser in a textual form or spoken form. These user questions can describeinformation that the user is interested in and the type of presentationthat the user desires to view the information in. In this regard, thebuilding system can identify, based on components of the user questionthat describe the information, the information that the user wishes toreceive. Furthermore, based on components of the user question thatdescribe the preferred presentation format, the system can compose aresponse based on the information and provide the composed response to auser via a user device.

In some embodiments, the questions asked by the user need to beinterpreted with contextual information of a building. For example, thequestions, by themselves, may not include enough information to identifythe information that the user is seeking. In this regard, the buildingsystem can utilize a building knowledge graph, a graph data structurethat represents contextual information of a building, equipment of thebuilding, users, events occurring within the building, etc. In thisregard, certain components, i.e., words or phrases of the user question,can be interpreted with the context of the building knowledge graph.Interpreting the components with the context of the building knowledgegraph may result in an identification of the information that the useris seeking and sources (e.g., databases, data nodes of the knowledgegraph, etc.). The system can then retrieve the information from thesources and compose a presentation for the user.

In some embodiments, the presentation provided to the user isdynamically determined. For example, the format for presentation, i.e.,audio presentation, textual presentation, graphical presentation, etc.can be identified from the user question. For example, some componentswithin the question, such as “plot,” “show,” “illustrate” may indicatethat the user is interested in a graphical representation of theinformation. Based on the presence of such components, the system cangenerate a graphical presentation for the information.

In addition to responding to user questions, the system can pushinformation to the user. For example, when new equipment data isreceived from equipment of a building, the equipment data may trigger arule. For example, a fault rule may trigger if a data point receivedfrom the equipment indicates a fault. In some embodiments, the systemcan perform machine learning to identify what insights that a particularuser may be interested in. Triggering an insight or learning an insightthrough machine learning algorithms can cause the system to proactivelypush the insight to the user, i.e., the user may receive the insightwithout directly requesting the insight from the system. The pushedinsights may be based on the contextual information of the buildingrepresented in the knowledge graph. For example, if the knowledge graphindicates that a particular user is a building owner and another user isan employee who has an office in the building, that building owner maybe interested in insights for the building that save energy for thebuilding. Energy savings insights can be generated by the system andpushed to the building owner. However, for the employee of the building,the energy insights may not be applicable and thus the system may notpush the energy insights to the user.

Conversational assistants such as Siri, Cortana, the Google Assistant,and Alexa lack the ability to utilize contextual information of abuilding when responding to user questions. Advantageously, the abilityto utilize contextual information can allow the building systemdescribed herein to respond to questions that a conventionalconversational assistant would not be able to respond to. For example,the question, “Show me faults for my equipment,” could be interpretedagainst the context of the building to identify what pieces of equipmentare owned or under the supervision of the person asking the question.Because a conventional conversational assistant does not have suchcontext, the conversational assistant would not be able to ask thequestion.

This application is related to U.S. patent application Ser. No.16/688,819 filed Nov. 19, 2019, U.S. patent application Ser. No.16/260,078 filed Jan. 28, 2019, U.S. patent application Ser. No.16/008,885 filed Jun. 14, 2018, U.S. patent application Ser. No.16/014,936 filed Jun. 21, 2018, U.S. Provisional Patent Application No.62/929,610 filed Nov. 1, 2019, and U.S. patent application Ser. No.15/586,104 filed Jun. 3, 2017, the entirety of each of which isincorporated by reference herein.

Referring now to FIG. 1, a UI-less UX system 100 of a building 102including a dynamic UX service 120 and a knowledgebase 118 is shown,according to an exemplary embodiment. The system 100 is configured toreceive user questions from a user device 124 of a user and composeresponses for presentation to the user via the user device 124, in someembodiments. The building 102 may be a commercial or residentialbuilding, e.g., a house, an apartment complex, a school, an officebuilding, a museum, a gallery, a sky rise, etc. The building 102 canincludes spaces 104, assets 106, and people 108.

The spaces 104 may be areas of the building 102, for example, rooms,hallways, conference rooms, floors, parking areas, etc. The assets 106may be equipment of the spaces 104, e.g., HVAC devices, securitydevices, fire suppression devices, surveillance devices, etc. Examplesof the assets 106 may be devices that can communicate, e.g., via anetwork, to a data ingestion service 116 of the system 100, i.e., theedge devices 110-114. Furthermore, the building 102 includes, or isassociated with, people 108. The people 108 may be building owners,building occupants, building tenants, building workers (e.g.,technicians, repair people, building managers, etc.).

The system 100 includes the data ingestion service 116, theknowledgebase 118, and an dynamic UX service 120. Each of the components116-120 and 126 can be implemented across one or multiple servers and/orlocal systems. For example, the components 116-120 and 126 can bedistributed across multiple physical computing systems and/or devices orlocated within a common computing infrastructure. For example, thecomponents 116-120 and 126 can be implemented in MICROSOFT AZURE, AMAZONWEBSERVICES, and/or any other cloud computing system. Each of thecomponents 116-120 can be implemented on processing circuits and/ormemory devices. For example, data ingestion service 116 is shown toinclude one or multiple processors 134 and one or multiple memorydevices 136. Similarly, the dynamic UX service 120 can include one ormultiple processors 138 and/or one or multiple memory devices 140.

The processors can be a general purpose processor, an applicationspecific integrated circuit (ASIC), one or more field programmable gatearrays (FPGAs), a group of processing components, or other suitableelectronic processing components. The processor can be communicativelycoupled to the memory. The memory can include one or more devices (e.g.,memory units, memory devices, storage devices, etc.) for storing dataand/or computer code for completing and/or facilitating the variousprocesses described in the present disclosure. The memory can includerandom access memory (RAM), read-only memory (ROM), hard drive storage,temporary storage, non-volatile memory, flash memory, optical memory, orany other suitable memory for storing software objects and/or computerinstructions. The memory can include database components, object codecomponents, script components, or any other type of informationstructure for supporting the various activities and informationstructures described in the present disclosure. The memory can becommunicably connected to the processor via the processing circuit andcan include computer code for executing (e.g., by the processor) one ormore processes described herein.

The knowledgebase 118 can be a database system storing information ofthe building 102. The knowledgebase 118 can be a graph database (GDB).The knowledgebase 118 can be in a Resource Desorption Framework (RDF)format. Furthermore, the knowledgebase 118 can be based on the BRICKschema. Furthermore, the knowledgebase 118 can be a relational database,an object database, a distributed database, a NoSQL database, and/or anyother type of database.

The knowledgebase 118 can be a digital twin of the building 102 or ofspecific entities of the building 102. The digital twin can provide avirtual representation of information of the building 102, e.g., aliving and adapting digital knowledgebase of the state of the building102. The digital twin can provide a virtual representation of equipment,spaces, people, and/or events associated with, or located in, thebuilding 102.

The knowledgebase 118 can store timeseries data 142 that may becollected from the edge devices 110-114 (e.g., temperature data, controldecisions, occupancy data, security data, etc.). The timeseries data 142may be time correlated, i.e., a series of data samples each linked to atime stamp indicating when the data sample was recorded by the edgedevices 110-114. The knowledgebase 118 can further store buildingcontext 144, i.e., information describing the building 102, i.e., thespaces 104, the assets 106, and the relationships between the spaces 104and/or the assets 106. Furthermore, the building context 144 can includeuser context 146, i.e., information describing the people 108 of thebuilding 102 and/or the relationships between the spaces 104, the assets106, and/or the people 108.

The data ingestion service 116 is shown to collect data from the edgedevices 110-114 of the building 102 and ingest the information into theknowledgebase 118. For example, the timeseries data 142 could becollected by the data ingestion service 116 from the edge device 110 andstored in the knowledgebase 118. The data ingestion service 116 maystore logic for identifying where in the knowledgebase 118 to storedata, i.e., what devices, spaces, or people to relate the collected datato in the knowledgebase 118. In addition to collecting data from theedge devices 110-114 and ingesting the collected data of the edgedevices 110-114, the data ingestion service 116 can ingest data fromother systems, e.g., from human resource systems, social media systems,tenant billing systems, room scheduling systems, and/or any other systemthat stores contextual information of the building 102 and/or entitiesassociated with the building 102.

Based on the information ingested and stored by the knowledgebase 118,the dynamic UX service 120 can generate one or multiple presentations122 for providing to the user device 124. The presentations 122 can betextual based responses, visual responses, and/or audio based responsesto questions that a user of the user device 124 provides to the dynamicUX service 120 via the user device 124. In this regard, the dynamic UXservice 120 can be configured to decompose a question provided by theuser device 124 into a presentation context and a requested informationcontext where the presentation context describes the presentation format(e.g., graphic based, text based, audio based) that the user desires andthe requested information context (e.g., what faults, to-dos, or otherinformation that the user is interested in).

In some embodiments, the dynamic UX service 120 performs analytics ondata retrieved from the knowledgebase 118 to surface insights to theuser device 124. In some embodiments, the dynamic UX service 120performs the analytics by communicating with analytics engine service126. The analytics engine service 126 can, upon request by the dynamicUX service 120, instantiate one of multiple analytics algorithms, i.e.,the analytics engine 128, the analytics engine 130, and/or the analyticsengine 132 to perform the analytics for the dynamic UX service 120 andreturn a result of the analytics algorithm. The result may be pushed bythe analytics engine service 126 back to the dynamic UX service 120 forpresentation to the user.

In some embodiments, the analytics performed by the analytics engineservice 126 could be equipment vibration analysis where faults orimprovements for equipment can be derived from vibration data stored inthe knowledgebase 118. Examples of the vibration analysis that theanalytics engine service 126 could perform can be found in U.S. patentapplication Ser. No. 15/993,331 filed May 30, 2018 which is incorporatedby reference herein in its entirety.

In some embodiments, the analytics performed by the analytics engineservice 126 are performed by cognitive agents (i.e., each of the engines128-132 are agents), machine learning modules deployed to performanalytics. Examples of agents can be found in U.S. patent applicationSer. No. 16/036,685 filed Jul. 16, 2018, U.S. patent application Ser.No. 16/533,499 filed Aug. 6, 2019, and U.S. patent application Ser. No.16/533,493 filed Aug. 6, 2019, the entireties of which are incorporatedby reference herein.

In some embodiments, the analytics performed by the analytics engineservice 126 include building load forecasting and/or building loadprediction model training for the building 102. In this regard, the loadforecasting and model training described in U.S. patent application Ser.No. 16/549,037 filed Aug. 23, 2019, U.S. patent application Ser. No.16/549,744 filed Aug. 23, 2019, U.S. patent application Ser. No.16/549,656 filed Aug. 23, 2019, U.S. patent application Ser. No.16/115,120 filed Aug. 28, 2018, and U.S. patent application Ser. No.16/115,282 filed Aug. 28, 2018 can be performed by the analytics engineservice 126, the entirety of each of which is incorporated by referenceherein.

In some embodiments, the analytics performed by the analytics engineservice 126 include equipment fault prediction. For example, theequipment fault prediction may be chiller fault prediction, e.g., thechiller fault prediction and model management and training as describedwith reference to U.S. patent application Ser. No. 16/198,456 filed Nov.21, 2018, U.S. patent application Ser. No. 16/198,416 filed Nov. 21,2018, and U.S. patent application Ser. No. 16/198,377 filed Nov. 21,2018, the entireties of which are incorporated by reference herein.

In some embodiments, the analytics performed by the analytics engineservice 126 includes processing risk information, e.g., threat data, andgenerating risk scores for building assets, e.g., the spaces 104, theassets 106, and/or the people 108. Examples of the risk analytics thatthe analytics engine service 126 can be configured to perform are foundin U.S. patent application Ser. No. 16/143,037 filed Sep. 26, 2018, U.S.patent application Ser. No. 16/143,221 filed Sep. 26, 2018, U.S. patentapplication Ser. No. 16/143,276 filed Sep. 26, 2018, U.S. patentapplication Ser. No. 16/143,256 filed Sep. 26, 2018, U.S. patentapplication Ser. No. 16/143,274 filed Sep. 26, 2018, U.S. patentapplication Ser. No. 16/143,283 filed Sep. 26, 2018, U.S. patentapplication Ser. No. 16/143,247 filed Sep. 26, 2018, U.S. patentapplication Ser. No. 16/143,282 filed Sep. 26, 2018, U.S. patentapplication Ser. No. 16/255,719 filed Jan. 23, 2019, and U.S. patentapplication Ser. No. 16/269,274 filed Feb. 6, 2019, the entirety of eachof which is incorporated by reference herein.

In some embodiments, the analytics performed by the analytics engineservice 126 includes processing security system data to detect whetheractions can be taken to reduce false alarms in the building 102.Examples of false alarm reduction based analytics can be found in U.S.patent application Ser. No. 15/947,725 filed Apr. 6, 2018, U.S. patentapplication Ser. No. 15/947,722 filed Apr. 6, 2018, U.S. patentapplication Ser. No. 16/172,371 filed Oct. 26, 2018, U.S. patentapplication Ser. No. 16/368,620 filed Mar. 28, 2019, and U.S. patentapplication Ser. No. 16/417,359 filed May 20, 2019, the entirety of eachof which is incorporated by reference herein.

In some embodiments, the analytics performed by the analytics engineservice 126 include assurance services to detect faults and/or determineactionable insights for improving the performance of building equipment.Examples of assurance services processing that the analytics engineservice 126 can be configured to perform can be found in U.S. patentapplication Ser. No. 16/142,472 filed Sep. 26, 2018 and U.S. patentapplication Ser. No. 16/583,966 filed Sep. 26, 2019, the entireties ofwhich are incorporated by reference herein.

Furthermore, in some embodiments, the analytics performed by theanalytics engine service 126 include timeseries processing analytics.Examples of timeseries processing that the analytics engine service 126can be configured to perform can be found in U.S. patent applicationSer. No. 15/644,519 filed Jul. 7, 2017, U.S. patent application Ser. No.15/644,581 filed Jul. 7, 2017, and U.S. patent application Ser. No.15/644,560 filed Jul. 7, 2017, the entirety of each of which areincorporated by reference herein.

In some embodiments, the analytics engine service 126 can perform modelpredictive maintenance (MPM) where equipment is controlled, serviced, orreplaced in such a manner to improve the performance of the equipmentand meet financial incentives. Examples of MPM that the analytics engineservice 126 can be configured to perform can be found in U.S. patentapplication Ser. No. 15/895,836 filed Feb. 13, 2018, U.S. patentapplication Ser. No. 16/232,309 filed Dec. 26, 2018, U.S. patentapplication Ser. No. 16/418,686 filed May 21, 2019, U.S. patentapplication Ser. No. 16/438,961 filed Jun. 12, 2019, U.S. patentapplication Ser. No. 16/449,198 filed Jun. 21, 2019, U.S. patentapplication Ser. No. 16/457,314 filed Jun. 28, 2019, and U.S. patentapplication Ser. No. 16/518,548 filed Jul. 22, 2019, the entirety ofeach of which is incorporated by reference herein.

Furthermore, the user, via the user device 124 can provide feedback tothe system 100. For example, the feedback may be a follow-on question toa first question asked by the user, e.g., asking for more detailedinformation, indicating that the response provided by the dynamic UXservice 120 is inaccurate, etc. Furthermore, the feedback can beindicative of actions performed by the user. For example, if thepresentation 122 prompts the user to replace a component of the edgedevice 114, the feedback to the dynamic UX service 120 may be anindication that the user has performed the action. In some embodiments,rather than directly providing the feedback, an action such as replacinga component can be detected by the edge device 114 and provided by theedge device 114 to the dynamic UX service 120.

In some embodiments, rather than, or in addition to responding to a userquestion, the dynamic UX service 120 can be configured to deriveinsights and push the insights to the user device 124. For example, thedynamic UX service 120 may store a set of rules that indicate a fault oraction that a user should take to repair equipment or improve theperformance of the equipment. When new data is ingested into theknowledgebase 118, the dynamic UX service 120 can be configured to runthe set of rules against the new data to see if any of the rules aretriggered by the new data. A triggered rule may indicate a fault,action, or other insight for a user to review. Based on the insightidentified in the triggered rule, the dynamic UX service 120 can beconfigured to generate a presentation indicating the triggered rule tothe user device 124. In some embodiments, the presentation is based onboth the triggered rule and the new data, for example, an indication ofthe insight in addition to the new data that triggered the rule. In someembodiments, the presentation is based on the identity of the user thatthe presentation is destined for. For example, if a user generally asksfor charts or visualizations, the dynamic UX service 120 can generate avisualization for the triggered rule. However, if the user frequentlyrequests spoken word presentation, the dynamic UX service 120 maycompose an audio presentation of the triggered rule.

In some embodiments, the dynamic UX service 120 performs a machinelearning algorithm to derive insights for presentation to the user. Themachine learning algorithm may identify, based on historical questionsof a user, what types of information a user might be interested in. Forexample, if a user frequently provides questions to the dynamic UXservice 120 for energy usage information, the machine learning algorithmmay identify that energy savings is important to the user. The machinelearning algorithm may run equipment simulations and/or perform otheranalysis that result in improved equipment settings or schedules thatsave energy. Such an insight can be composed into a presentation by thedynamic UX service 120 and pushed to the user device 124.

Rather than requiring predefined analyzers, the system 100 can utilizethe dynamic UX service 120 which can dynamically derive information forpresentation to the user via the user device. Furthermore, rather thanrequiring a predefined user interface service that provides astandardized information presentation, the dynamic UX service 120 candynamically identify an appropriate or desired presentation format forinformation requested by the user and dynamically generate thepresentation 122 for presentation to the user based on the derivedcontext indicating the appropriate presentation format.

In some embodiments, the knowledgebase 142 stores a question graph datastructure indicating historical questions asked by a user or multipleusers. The graph data structure may include nodes representing possiblequestions that a user may ask and nodes representing various users.Relationships between a particular user node and each of the possiblequestions may have a weight value indicating how frequently a user asksa particular question. The dynamic UX service 120, in some embodiments,is configured to analyze the question graph data structure to identify aquestion that a user may not have asked but would be interested in.

For example, if a building manager of a first building has arelationship greater than a predefined amount between a noderepresenting the first building manager and an energy savings question,but a second building manager of a second building, represented by asecond building manager node, does not have a relationship greater thanthe predefined amount between the node representing the second buildingmanager and the energy savings question, the dynamic UX service 120 mayidentify that the second building manager may be interested in energysavings for the second building. This identification can be generated bythe dynamic UX service 120 since the energy savings question isimportant to the first building manager and the first building managerand the second building manager fulfill similar roles in the first andsecond buildings. The dynamic UX service 120 may generate energy savingsinformation pertaining to the second building and automatically push theenergy savings information to a user device of the second buildingmanager.

Referring now to FIG. 2, a question 200 is provided by the user device124 to the dynamic UX service 120, according to an exemplary embodiment.The question 200 is a textual input, i.e., “Show me faults forController A.” In some embodiments, the user types the question 200 intothe user device 124. In some embodiments, the user speaks the question200 into the user device 124 and the audio is translated into textualdata by the user device 124 and/or the dynamic UX service 120. Thequestion 200 specifies that the user wishes to be shown information,that the user is interested in fault information, and that the user isinterested in a particular device of the building 102, i.e., acontroller labeled “A.”

Referring now to FIG. 3, a question 300 is provided by the user device124 to the dynamic UX service 120, according to an exemplary embodiment.The question 300 is a textual input, i.e., “Tell me faults forController A.” In some embodiments, the user types the question 300 intothe user device 124. In some embodiments, the user speaks the question300 into the user device 124 and the audio is translated into textualdata by the user device 124 and/or the dynamic UX service 120. Thequestion 300 specifies that the user wishes to be told information, thatthe user is interested in fault information, and that the user isinterested in a particular device of the building 102, i.e., acontroller labeled “A.”

Referring now to FIG. 4, a graph data structure 400 is shown, accordingto an exemplary embodiment. The graph data structure 400 can be anexample of the knowledgebase 118 or a component of the knowledgebase118. The graph data structure 400 includes multiple nodes and edges,i.e., nodes 402-408 and edges 410-414. The nodes 402-408 represententities of the building 102, i.e., data, equipment, areas, and thebuilding 102 itself. The nodes 402-408 include a controller A node 404,a fault data node 402, a zone A node 406, and a building node 408.

The controller A node 404 is associated with the fault data node 402 viathe has edge 414, indicating that the controller A has generated or isotherwise associated fault data. The controller A node 404 is associatedwith the zone A node 406 via the serves edge 410, indicating that thecontroller A operates to control the zone A. Furthermore, the zone Anode 406 is associated with the building node 408 via the isLocatedInedge 412, indicating that the zone A is a zone of the building.

Referring now to FIG. 5, the dynamic UX service 120 shown in greaterdetail processing the questions 200 and 300 and for composing apresentation for the user device, according to an exemplary embodiment.The dynamic UX service 120 includes a decomposition engine 500, a queryengine 502, and a presentation composer 504. The decomposition engine500 is configured to decompose the question strings of questions 200 and300 into multiple components, in some embodiments. The components may bewords or phrases. In some embodiments, the components either describerequested information context or presentation context. The componentsdescribing the presentation context can be provided by the decompositionengine 500 to the presentation composer 504 while the componentsdescribing the requested information context can be provided to thequery engine 502.

In some embodiments, the decomposition engine 500 includes a questioncache 508. The question cache 508 can be configured to store informationpertaining to historical questions of the user of the user device 124.In this regard, if the user asks two questions that are the same orsimilar, rather than decomposing the question, the decomposition engine500 can instruct the presentation composer 504 to present the previouspresentation instead of creating the same presentation twice andunnecessarily using processing resources. In some embodiments, thequestion cache 508 may store information pertaining to historicalquestions of users other than the user of the user device 124. Forexample, upon receiving a question from the user device 124, thedecomposition engine 500 may determine whether the question cache 508includes the same or a similar question and, if so, utilize part or allof the presentation data from the prior presentation to the same/similarquestion to generate the presentation for the current question. In someimplementations, if the previous question was from a different user, thedecomposition engine 500 may determine whether the presentation shouldbe changed based on the identity of the user (e.g., if the priorquestion requested data specific to the prior user or was customized tothe preferences of that user).

The query engine 502 can be configured to query the knowledgebase 118based on the components received from the decomposition engine 500. InFIG. 5, the components are “Controller A” and “Faults.” In someembodiments, the query engine 502 is configured to further query theknowledgebase 118 based on the components “Show me” and “Tell me” toretrieve data appropriate to be presented visually, in the case of thecomponent “Show me,” and retrieve data appropriate to be presented intext, i.e., in the case of the component “Tell me.” The query engine 502is configured to query the knowledgebase 118 based on the components andreceive a result from the knowledgebase 118. The query engine 502 isconfigured to provide the result to an analytics manager 506 and/or thepresentation composer 504, in some embodiments.

In some embodiments, the query engine 502 surfaces a confirmationrequest to the user device 124. The confirmation request can requestthat the user of the user device 124 confirm that the result datapertains to the question (e.g., the question 200 or the question 300)that the user has asked. In some embodiments, the query engine 502generates a confidence score indicating a probability that the result ofquerying the knowledgebase 118 has resulted in data that properlyresponds to the questions 200 and/or 300. In some embodiments, if theconfidence score is less than a predefined level, the query engine 502is configured to send the confirmation request to the use device 124. Insome embodiments, the query engine provides the confidence score alongwith the result of the query to the analytics manager 506 and/or thepresentation composer 504. In some embodiments, the presentationcomposer 504 can generate the presentation to include an indication ofthe confidence score.

In response to receiving approval from the user device 124, the queryengine 502 and proceed with pushing the result to the analytics manager506. In some embodiments, the user may disapprove of the query resultand provide additional contextual information that the query engine 502can be configured to use to query the knowledgebase 118 a second time toretrieve new result data. The new result data can be pushed to theanalytics manager 506.

The analytics manager 506 can be configured to communicate with theanalytics engine service 126 based on the result received from the queryengine 502 and cause an analytics engine to be instantiated by theanalytics engine service 126. The analytics engine service 126 can beconfigured to perform analytics based on the result provided by thequery engine 502 to generate an analytics result which can be returnedto the analytics manager 506. The analytics manager 506 can push theanalytics result, along with the original result from the query engine502, to the presentation composer 504 for composing the presentation tosend to the user device 124. In some embodiments, the analyticsperformed by the analytics engine service 126 requires additional dataof the knowledgebase 118. In this regard, the analytics manager 506 canbe configured to query the knowledgebase 118 for information for use inthe analytics performed by the analytics engine service 126 and providethe additional data to the analytics engine service 126 for processing.

Based on the result received from the query engine 502 and thecomponents received from the decomposition engine 500, the presentationcomposer 504 is configured to generate a presentation to provide to theuser device 124. The presentation composer 504 can format the resultreceived from the query engine 502 according to the presentation contextreceived from the decomposition engine 500. For example, when thepresentation context is “Show me,” the presentation composer 504 cangenerate one or more graphic representations of the result and providethe graphic presentations to the user device 124. When the presentationcontext is “Tell me,” the presentation composer 504 can generate atextual and/or audio description of the result for providing to the userdevice 124.

Referring now to FIG. 6, the graph data structure 400 of FIG. 4illustrating nodes and edges of the graph data structure 400 queried bythe query engine 502 to answer the questions 200 and/or 300 is shown,according to an exemplary embodiment. The query engine 502 can generatea query data structure based on the components received from thedecomposition engine 500, i.e., the component “Controller A” can be aparameter of the query indicating that the query should find informationrelated to “Controller A.” The component “Faults” may indicate the typeof information that the query should return, i.e., fault data.

The query of the query engine 502 identifies the node 404 and the edge412 to identify the fault data node 402. The knowledgebase 118 canreturn the fault data node 402 as the result. The fault data can beprovided by the query engine 502 to the presentation composer 504 forcomposition into a response by the presentation composer 504.

Referring now to FIGS. 7-9, examples 700-900 are shown of a conversationbetween the user via the user device 124 and the dynamic UX service 120illustrating the question 200 and the response composed for the question200 by the presentation composer 504, according to an exemplaryembodiment. In FIG. 7, the user provides a prompt 702, i.e., “Show mefaults for Controller A,” the question 200. In FIG. 8, in response tothe question 200, the presentation composer 504 sends a presentation tothe user device 124 that the user device 124 displays, i.e., theelements 704 and 706. The presentation composer 504 formats the responseto the questions 200 as graphical elements 704 and 706 because the userused the phrase “Show me” in the question 200. In FIG. 9, the userprovides a follow-on question to the dynamic UX service 120, “Show medetails on the network fault,” element 708. The element 708 requestsadditional information on the network fault shown in element 704. Thedynamic UX service 120 generates the element 710 which providesadditional details on the identified fault of the element 708. Again,the information is presented as a graphical output since the user usesthe phrase “Show me” in the element 708.

Referring now to FIGS. 10-12, examples 1000-1200 are shown of aconversation between the user via the user device 124 and the dynamic UXservice 120 illustrating the question 300 and the response composed forthe question 300 by the presentation composer 504, according to anexemplary embodiment. In FIG. 10, the user provides a prompt 1002, i.e.,“Tell me faults for Controller A” the question 300. In FIG. 11, inresponse to the question 300, the presentation composer 504 sends apresentation to the user device 124 that the user device 124 displays,i.e., the element 1004. The presentation composer 504 formats theresponse to the questions 200 as a textual description of faults becausethe user used the phrase “Tell me” in the question 300. In FIG. 11, theuser provides a follow-on question to the dynamic UX service 120, “Tellme more about the network offline fault,” element 1006. The element 1006requests additional information on the network fault described inelement 1004. The dynamic UX service 120 generates the element 1008which provides additional textual details on the identified fault of theelement 1006. Again, the information is presented as a textualdescription since the user uses the phrase “Tell me” in the element1006.

Referring now to FIG. 13, a question 1300 is provided by the user device124 to the dynamic UX service 120, according to an exemplary embodiment.The question 1300 is a textual input, i.e., “Show me my faults on floor3 by priority.” In some embodiments, the user types the question 1300into the user device 124. In some embodiments, the user speaks thequestion 1300 into the user device 124 and the audio is translated intotextual data by the user device 124 and/or the dynamic UX service 120.The question 1300 specifies that the user wishes to be showninformation, that the user is interested in fault information that isassociated in some to the user, and that the user is interested in faultinformation of a particular floor of a building, floor 3, and that theuser wishes for the faults to be sorted according to priority.

Referring now to FIG. 14, a graph data structure 1400 is shown,according to an exemplary embodiment. The graph data structure 1400 canbe an example of the knowledgebase 118 or a component of theknowledgebase 118. The graph data structure 1400 includes multiple nodesand edges, i.e., nodes 1402-1430 and edges 1432-1456. The nodes1402-1430 represent entities of the building 102, i.e., data, equipment,areas, and people associated with the building 102.

The graph data structure 1400 includes a John node 1402 representing auser “John.” The John node 1402 has a relationship to the HVAC devicenode 1404, i.e., John is responsible for the HVAC devices indicated bythe isResponsibleFor edge 1432. The controller A node 1406 hasrelationships to the HVAC device node 1404, the zone A node 1410, andthe fault data node 1412. The controller A 1406 is a type of HVACdevice, indicated by the edge isATypeOf 1434 between the node 1406 andthe node 1404. Furthermore, the controller A controls conditions of thezone A, indicated by the serves edge 1440 between the node 1406 and thenode 1410. Furthermore, the graph data structure 1400 stores fault datafor the controller A, indicated by the node 1412. The fault data isassociated with the controller A via the edge 1436. The zone A islocated on a floor 3 of the building 102, indicated by the relationshipisLocatedOn 1442 between the zone A node 1410 and the floor 3 node 1418.

The VAV 2 node 1416 represents a particular VAV of the building 102. TheVAV 2 operates temperature for a particular zone of the floor 3, zone Brepresented by zone B node 1414. The relationship between the VAV 2 andthe zone B is indicated by the controlsTemperatureIn edge 1444 betweenthe node 1416 and the node 1414. The VAV 2 has a damper component,represented by the damper node 1426. The damper is linked to the VAV 2by the edge hasA 1448 between the node 1416 and the node 1426.Furthermore, because the VAV 2 is a type of HVAC device, the isATypeOfedge 1460 is included between the node 1416 and the node 1404. Thedamper of the VAV 2 may have fault data associated with it, representedby the fault data node 1424 and the edge between the node 1426 and thenode 1424, the has edge 1450. Furthermore, the zone B is a zone of thefloor 3, to illustrate this relationship, the graph data structure 1400includes the isLocatedOn edge 1446 between the node 1414 and the node1418.

The graph data structure 1400 includes a zone C node 1420 representinganother zone of the building 102. The zone C is located on the floor 3.To illustrate the location of the zone C, the graph data structure 1400includes edge 1452 between the node 1420 and the node 1418. Furthermore,the zone C may have a door, i.e., door 11 represented by the door 11node 1428. To indicated that the door 11 is a door of the zone C, thegraph data structure 1400 includes the hasA edge 1454 between the node1420 and the node 1428. The door 11 may be a locking door and mayinclude a door lock. The door lock is represented by the door lock node1420. The door lock is associated with the door 11 by the hasA edge 1456between the node 1428 and the node 1430.

Because the door lock is a type of security device, the door lock can belinked to the security device node 1422 via the isATypeOf edge 1458.Furthermore, a particular user may be responsible for the securitydevices of the building 102. The user may be indicated by the Steve node1408. The responsibility of Steve may be indicated by theisResponsibleFor edge 1438 between the node 1408 and the node 1422.

Referring now to FIG. 15, the dynamic UX service 120 is shown in greaterdetail processing the question 1300 and composing a visual presentationfor the user device, according to an exemplary embodiment. Thedecomposition engine 500 is configured to decompose the question stringsof questions 1300 into multiple components, in some embodiments. Thecomponents are “Show me,” “Priority,” “My,” “Faults,” and “Floor 3.” Thecomponents describing the presentation context, i.e., “Show me” and“Priority,” are provided by the decomposition engine 500 to thepresentation composer 504 while the components describing the requestedinformation context, i.e., “My,” “Faults,” and “Floor 3,” are providedto the query engine 502.

The query engine 502 includes a query data structure 1500 used by thequery engine 502 to query the knowledgebase 118 for a result to providethe presentation composer 504. The query data structure 1500 can begenerated by the query engine 502 based on the requested informationcontext and context retrieved from the knowledgebase 118 by the queryengine 502. For example, the query engine 502 may need to understandwhat nodes of a graph data structure correspond to what componentsreceived from the decomposition engine 500. For example, “My” may referto a particular user, e.g., John, which the query engine 502 analyzesthe knowledgebase 118 to determine.

Based on the result received from the query engine 502 and thecomponents received from the decomposition engine 500, the presentationcomposer 504 is configured to generate a visual presentation to provideto the user device 124 in response to the question 1300. Thepresentation composer 504 can format the result received from the queryengine 502 according to the presentation context received from thedecomposition engine 500. For example, the presentation context is “Showme,” the presentation composer 504 can generate one or more graphicrepresentations of the result and provide the graphic presentations tothe user device 124. Furthermore, the presentation context includes a“Priority” component. The presentation composer 504 can be configured tosort the result data received from the query engine 502 to orderinformation in the visual presentation according to priority level,i.e., the presentation composer 504 can either retrieve a priority levelfor each result and/or generate a priority level for each result andsort the results in descending order of priority.

In some embodiments, the presentation composer 504 and/or the analyticsmanager 506 is configured to generate a monetization metric for each ofthe faults. For example, the monetization metric may indicate an expenseloss caused by the fault. In this regard, the presentation composer 504can rank the faults in order of descending expense loss such that thepresentation generated by the presentation composer 504 highlights thefaults that cause the most monetary loss, i.e., show the faults thatcause the greatest monetary loss at the top of a list or other display.In some embodiments, a user may provide a question to the dynamic UXservice 120 asking for finance information of particular faults. Inresponse to the request, the analytics manager 506 and/or thepresentation composer 504 can generate the monetization metric andpresent the monetization metric to the user via the user device 124.

In some embodiments, the presentation can be sorted with a scoringalgorithm. The scoring algorithm can be executed by the presentationcomposer and/or the analytics manager 506. For example, the scoringalgorithm can take into account a criticality of an asset affected by afault, i.e., how important the asset is to the building, a location of aspace where the asset is located (e.g., on an engineering floor versus acustomer floor), or the users that the asset affect (e.g., an assistantversus a company vice president). The scoring algorithm can be executedby the presentation composer and/or the analytics manager to generate ascore for each fault and sort the faults by the generated scores.

Referring now to FIGS. 16-17, the graph data structure 1400 of FIG. 14illustrating nodes and edges of the graph data structure 1400 queried bythe query engine 502 to build the query data structure 1500 is shown,according to an exemplary embodiment. The query engine 502 can generatethe query data structure based on the components received from thedecomposition engine 500, i.e., the components “My,” “Floor 3,” and“Faults” can be used by the query engine 502 to determine parameters1700-1704 of the query data structure 1500 indicating that the queryshould find information related to “John” and “Floor 3.” The component“Faults” may indicate the type of information that the query shouldreturn, i.e., fault data indicated by the parameter 1704.

In some embodiments, the query engine 502 needs to search and/or querythe graph data structure 1400 to determine the parameters 1700 and 1702.For example, the parameter 1700 can be identified by finding which nodeof the graph data structure 1400 is associated with “My” i.e., the usersubmitting the question 1300, John, indicated by the node 1402. Thecomponent floor 3 can be used to search the graph data structure 1400 todetermine whether one of the nodes corresponds to a third floor of thebuilding, i.e., node 1418.

In some embodiments, the query data structure 1500 includes an assumedtime indication. For example, the query data structure 1500 may includean indication that the faults queried by the query data structure 1500are active faults or faults that have not yet been resolved oraddressed. In some embodiments, the query data structure 1500 mayinclude a time window parameter, e.g., a predefined window of time toquery the faults, i.e., faults only occurring within the predefinedwindow. In some embodiments, the query data structure 1500 is generatedby the query engine 502 to include the predefined window of time unlessthe question asked by the user includes an indication of time. Forexample, a question that includes the phrase, “Show me all historicalfaults,” may cause the query engine 502 to generate the query datastructure 1500 to include no time window.

Referring now to FIG. 18, the graph data structure 1400 queried by thequery data structure 1500 is shown, according to an exemplaryembodiment. In FIG. 18, the bolded nodes and edges illustrate the nodesand edges traversed in response to the query data structure 1500 whilethe double bolded nodes, i.e., node 1412 and 1424, represent the resultof the queried, i.e., the data returned to the query engine 502. Thequery data structure 1500 can cause the knowledgebase 118 to return anyfault related data linked to both nodes 1402 and 1418, indicated byparameters 1700 and 1702 where the fault type of information to bereturned is indicated by the parameter 1704.

In some embodiments, the knowledgebase 118 includes a cache of all noderelationships of a graph. For example, the cache may indicate all nodesconnected to each node of the graph 1400, i.e., a projection ofrelationships for every node of the graph. For example, a cache forcontroller A node 1406 may indicate that the HVAC device node 1404, thezone A node 1410, and the fault data node 1412 are all connected to thecontroller A node 1406. In some embodiments, the cache may includeprojection of multiple relationship depths, for example, for a depth oftwo, the cache of controller A 1406 may indicate that fault data node1412, zone a node 1410, floor 3 node 1418, HVAC device node 1404, Johnnode 1402, and VAV box 2 node 1416 are all connected to the controller Anode 1406. In some embodiments, the parameters of the query datastructure 1500 indicating the John node 1402 and the floor 3 node17021702 may return two cache projections of related nodes. Theknowledgebase 118 can compare the two cache projections against eachother to find an intersection of fault data nodes, i.e., the fault datanode 1412 and the fault data node 1424, to return to the query engine502. In some embodiments, the cache may be stored as a redis cache.

Referring now to FIGS. 19-21, examples 1900-2100 are shown of aconversation between the user via the user device 124 and the dynamic UXservice 120 illustrating the question 1300 and the response composed forthe question 1300 by the presentation composer 504, according to anexemplary embodiment. In FIG. 19, the user provides a prompt 1902, i.e.,“Show me my faults on floor 3 by priority,” the question 1300. In FIG.20, in response to the question 1300, the presentation composer 504sends a presentation to the user device 124 that the user device 124displays, i.e., the element 1904. The presentation composer 504 formatsthe response to the question 1300 as a graphic element of two faultsbecause the user used the phrase “Show me” in the question 1300. Theelement 1904 includes indications of two faults “VAV Damper Stuck” and“Controller A Network Fault.” The “VAV Damper Stuck” element may beincluded above the “Controller A Network Fault” because the damper beingstuck may be a high priority fault than the network fault. Thepresentation composer 504 may sort the two faults based on prioritysince the user used the word “priority” in the question 1300.

In FIG. 20, the user provides a follow-on question to the dynamic UXservice 120, “Tell me more about the controller network fault,” element1906. The element 1906 requests additional information on the networkfault described in element 1904. The dynamic UX service 120 generatesthe element 1908 which shown in FIG. 21 provides additional textualdetails on the network fault and information indicating that althoughthe controller is experiencing a network fault, it is still operatingthe temperature of the zone A properly. The information is presented asa textual description of the controller network fault in the element1908 since the user uses the phrase “Tell me” in the element 1906.

Referring now to FIG. 22, a question 2200 is provided by the user device124 to the dynamic UX service 120, according to an exemplary embodiment.The question 2200 is a textual input, i.e., “Show my list of things Ineed to do before I go home.” In some embodiments, the user types thequestion 2200 into the user device 124. In some embodiments, the userspeaks the question 2200 into the user device 124 and the audio istranslated into textual data by the user device 124 and/or the dynamicUX service 120. The question 2200 specifies that the user wishes to beshown a task list that the user needs to address. The question 2200further provides a time constraint in the question 2200 indicating thatthe user only wants to see tasks that need to be completed before theuser leaves the building 102 and goes home for the day.

Referring now to FIG. 23, a graph data structure 2300 is shown,according to an exemplary embodiment. The graph data structure 2300 canbe an example of the knowledgebase 118 or a component of theknowledgebase 118. The graph data structure 2300 includes the nodes andedges of the graph data structure 1400 and further nodes 2302 and 2304an edges 2306, 2308, 2310, and 2312. The work schedule node 2302provides a work schedule for John. The relationship between the workschedule and John is indicated by the hasA edge 2306 and theisAssignedTo edge 2308. The work schedule may have particular workinghours, indicated by the hours node 2304. The has edge 2312 between thenode 2302 and the node 2304 indicates that the work schedule has thehours indicated by the node 2304.

The performsTestingOn edge 2310 between the John node 1402 and the HVACdevice node 1404 indicates that John is the individual that performstesting on the HVAC devices of the building 102, i.e., the controller Aand the VAV 2 1416. This dual edge, i.e., edge 1432 and 2310, indicatetwo separate duties of John, i.e., he is responsible for the HVACdevices and that he is the individual that performs testing on the HVACdevices.

Referring now to FIG. 24, the dynamic UX service 120 is shown in greaterdetail processing the question 2200 and composing a visual presentationfor the user device, according to an exemplary embodiment. Thedecomposition engine 500 is configured to decompose the question stringof question 2200 into the components “Show,” “List,” “My,” “Things,” “ToDo,” and “Before I Go Home.” The components describing the presentationcontext, i.e., “Show” and “List,” are provided by the decompositionengine 500 to the presentation composer 504 while the componentsdescribing the requested information context, i.e., “My,” “Things,” “ToDo,” and “Before I Go Home,” are provided to the query engine 502.

The query engine 502 includes a query data structure 2400 used by thequery engine 502 to query the knowledgebase 118 for a result to providethe presentation composer 504. The query data structure 2400 can begenerated based on the requested information context and contextretrieved from the knowledgebase 118 by the query engine 502. Forexample, the query engine 502 may need to understand what nodes of agraph data structure correspond to what components received from thedecomposition engine 500. For example, “My” may refer to a particularuser, e.g., John, “Things” may pertain to the HVAC devices that John isresponsible for, “To Do” may correspond to any action that need to beperformed on the HVAC devices, while “Before I Go Home” may provide anindication of a time constraint on the actions that need to beperformed.

Based on the result received from the query engine 502 and thecomponents received from the decomposition engine 500, the presentationcomposer 504 is configured to generate a visual presentation to provideto the user device 124 in response to the question 2200. Thepresentation composer 504 can format the result received from the queryengine 502 according to the presentation context received from thedecomposition engine 500. For example, the presentation context is“Show” and “List.” Accordingly, the presentation composer 504 cangenerate a graphic list of actions that need to be performed before theuser goes home for the day.

Referring now to FIGS. 25-26, the graph data structure 2300 of FIG. 23illustrating nodes and edges of the graph data structure 2300 queried bythe query engine 502 to build the query data structure 2400 is shown,according to an exemplary embodiment. The query engine 502 can generatethe query data structure 2400 based on the components received from thedecomposition engine 500, i.e., the components “My,” “Things,” “To Do,”and “Before I Go Home” can be used by the query engine 502 to determineparameters 2600-2606 of the query data structure 2400 indicating thatthe query should find information related to “John” and “HVAC Device.”The query engine 502 can search the graph data structure 2300 for “My”and determine that the user generating the question 2200 is John,represented by node 1402. The query engine 502 can cause the query datastructure 2400 to include an indication of the John node 1402, i.e., theparameter 2600.

The query engine 502 may search the graph data structure 2300 and findthat the John node 1402 is linked to the HVAC device node 1404 via theisResponsibleFor edge 1432. Based on this relationship, the query engine502 can set associate the “Things” component with the HVAC device node1404 and cause the query data structure 2400 to include an indication ofthe node 1404, i.e., parameter 2602. The component “To Do” may indicatethe type of information that the query should return, i.e., fault dataor any other information which indicates actions that need to beperformed by John indicated by the parameter 2604. The parameter 2604may indicate that the query should return information pertaining toactions that need to be performed. Furthermore, the query engine 502 maydetermine that the component “Before I Go Home” corresponds to aparticular time. To cause the query data structure 2400 to return thetime, the query engine 502 can cause the query data structure 2400 toinclude the parameter 2606.

Referring now to FIG. 27, the graph data structure 2300 queried by thequery data structure 2400 is shown, according to an exemplaryembodiment. In FIG. 27, the bolded nodes and edges illustrate the nodesand edges traversed in response to the query data structure 2400 whilethe double bolded nodes, i.e., node 2304, 1412, and 1424, represent theresult of the query, i.e., the data returned to the query engine 502.The query data structure 2400 can cause the knowledgebase 118 to returnany actionable data linked to both nodes 1402 and 1404, indicated byparameters 2600 and 2602 where the type of information to be returned isindicated by the parameter 2604. Furthermore, the query data structure2400 can cause the knowledgebase 118 to return the hours associated withthe user John indicated by the parameters 2600 and 2606.

Referring now to FIGS. 28-30, examples 2800-3000 are shown of aconversation between the user via the user device 124 and the dynamic UXservice 120 illustrating the question 2200 and the response composed forthe question 2200 by the presentation composer 504, according to anexemplary embodiment. In FIG. 28, the user provides a prompt 2800, i.e.,“Show my list of things I need to do before I go home,” the question2200. In FIG. 29, in response to the question 2800, the presentationcomposer 504 sends a presentation to the user device 124 that the userdevice 124 displays, i.e., the element 2802. The presentation composer504 formats the response to the question 2200 as a graphic list elementof two faults because the user used the phrase “Show me” and “list” inthe question 1300. The element 2802 includes a list including two items,a first action to “Repair stuck VAV damper” and second action “Repairoffline controller.” The “Repair stuck VAV damper” element may beincluded above the “Repair offline controller” because the damper beingstuck may be a high priority than the controller being offline and theuser may need to perform the actions in order of priority.

In FIG. 29, the user provide the prompt 2804 asking for additionaldetails on the to-do list of element 2802, i.e., “Can you tell medetails.” In FIG. 30, the dynamic UX service 120 responds to the prompt2804 with more details information on the two actions that the userneeds to perform, i.e., the element 2806. The elemtn2806 includes atextual description including the proper order for performing the steps,an indication of when the user will be leaving, and historicalinformation regarding the two pieces of equipment of the action list.

Referring again to FIG. 27, in some embodiments, the questions providedby the user device 124, may be questions asked by one user about anotheruser. For example, Steve, represented by the Steve node 1408 in FIG. 27,may ask questions about John, represented by the John node 1402. Forexample, a question such as, “Does John have any faults to attend to,”may cause the fault data node 1412 and/or the fault data node 1424 to bereturned. In some embodiments, to return the fault data of John, thesystem must first confirm that Steve has the ability to view informationabout John. For example, Steve may be associated with a “Supervisor”role, for example, a node “Supervisor” may exist in the graph datastructure 2300 with a relationship “isA” between the Steve node 1408 andthe “Supervisor” node. The relation of Steve to the supervisor role canbe identified by the query engine 502 to confirm that Steve can viewinformation about John. Similarly, a relationship “manages” may existbetween the Steve node 1408 and the John node 1402. The query engine 502can review the “manages” relationship to confirm that Steve can viewinformation about John.

In some embodiments, when changes are made to the graph data structure2300 by a first user that affects a second user, the dynamic UX service120 may push an notification of the update to the user. For example, ifJohn has a window installed in Zone C, represented by the zone C node1420, the knowledgebase 118 can cause a node “Window” to be added to thegraph data structure 2300 along with a relationship “hasA” between thezone C node 1420 and the “Window” node. Because Steve is responsible forsecurity in the Zone C, the dynamic UX service 120 can identify theupdate to the graph data structure 2300, identify that Steve is relatedto the Zone C and that a change has been made in Zone C, and generate apresentation for pushing to a user device of Steve.

Referring now to FIG. 31, a block diagram of the dynamic UX service 120and the analytics engine service 126 generating a presentation with aroot fault is shown, according to an exemplary embodiment. In FIG. 31,the analytics engine service 126 includes a nested fault engine 3100.The nested fault engine 3100 can be configured to utilize fault data ofthe knowledgebase 118 in analyzing multiple faults of a building and/orbuilding subsystem to identify relationships between the faults, i.e.,determine whether one fault causes another. The nested fault engine 126can construct a data structure that represents the relationships betweenmultiple faults indicated by data of the knowledgebase 118.

In some embodiments, a user, via the user device 124 provides a questionto the dynamic UX service 120 requesting fault data. For example, thequestion may be “Show me the faults that I need to address.” The dynamicUX service 120 can analyze the fault question and provide a request tothe analytics engine service 126. The analytics engine service 126 canrespond to the dynamic UX service 120 with a root fault, i.e., a mainfault that is responsible for other faults occurring. The dynamic UXservice 120 can compose a presentation data structure for presentationto the user via the user device 124. The presentation data structure caninclude an indication of the root fault. Decomposing a user question andcomposing a presentation for a user is described in greater detail inFIGS. 1-30.

In some embodiments, rather than providing a question to the dynamic UXservice 120, the dynamic UX service 120 may automatically push thepresentation with the root fault to the user device 124 withoutrequiring the user to first provide a request or question to the dynamicUX service 120. In this regard, the dynamic UX service 120 mayperiodically cause the nested fault engine 3100 to identify a root faultthat needs to be addressed, identify a user that is responsible foraddressing the root fault, and push a presentation with an indication ofthe root fault to the user.

In some embodiments, the dynamic UX service 120 can communicate with theanalytics engine service 126 to cause the analytics engine service 126to instantiate the nested fault engine 3100. The nested fault engine3100 can be configured to query the knowledgebase 118 for fault data. Insome embodiments, the nested fault engine 3100 queries the knowledgebase118 for data associated with the user of the user device 124, i.e., forfault data that the user is responsible for servicing. In someembodiments, the nested fault engine 3100 analyzes raw data in theknowledgebase 118 to identify the presence of a fault, i.e., the datamay not explicitly indicate a fault but may be raw temperaturemeasurements, network traffic data, heartbeat signals, etc.

The nested fault engine 3100 can analyze a set of identified faults toconstruct the nested fault tree 3102. In some embodiments, the nestedfault engine 3100 may store sets of preconfigured rules that indicatethat certain types of faults in one system cause other types of faultsin the same system. For example, in a system, a stuck damper of aparticular zone may be a first fault and a failure to meet a temperaturesetpoint for the particular zone may be a second fault. A rule may bestored by the nested fault engine 3100 that indicates that a stuckdamper fault causes a temperature setpoint fault. In some embodiments,to apply the rules, e.g., to understand that a particular damperexperiencing a fault is associated with a particular zone experiencing atemperature fault, the nested fault engine 3100 can equerry theknowledgebase 118 for contextual information, i.e., for relationshipsbetween equipment, people, spaces, etc.

The nested fault tree 3102 may be a data structured stored by the nestedfault engine 3100 and/or stored in the knowledgebase 118. The nestedfault tree 3102 can be constructed in a relationship form, e.g., graphdatabase form, where the faults are represented as nodes and the edgesrepresent the relationships between the nodes. The nested fault tree3102 can be a permanent piece of information that is stored and updatedas faults occur and are addressed. In some embodiments, the nested faulttree 3102 is stored by the nested fault engine 3100 for the purpose ofan analysis and is deleted once the analysis is complete. The nestedfault tree 3102 can be recreated by the analytics engine service 126when another analysis is conducted by the nested fault engine 3100.

The nested fault tree 3102 includes five faults but can include anynumber of faults with varying numbers of dependencies, i.e., one faultmay be caused by another fault, multiple faults can all be caused by onefault, or one fault can be caused by multiple other faults. In thenested fault tree 3102, a network engine power fault 3104 may exist. Thenetwork engine power fault 3104 may indicate that a network device thatmanages a network for a building is experiencing a power issue, i.e.,the device is off. Other devices connected to the network that thenetwork engine manages may experiencing errors since they may rely onthe network. For example, a controller that receives a temperaturesetpoint via the network may experience a network connection fault sincethe network managed by the network engine may be offline. This fault maybe indicated by a controller network connection fault 3106. Furthermore,because the controller is not receiving the setpoint, a user requestedsetpoint may never be delivered to the controller and a space operatedby the controller may never reach the user requested setpoint, causing aspace setpoint error, i.e., space temperature fault 3108.

A damper of a duct system may be a power over Ethernet (PoE) device andmay receive power via the network of the network engine. However,because the network engine is experiencing a power fault, the PoE dampermay not receive any power and may cease to operate properly. This maycause the PoE damper to go offline, resulting in the PoE damper offlinefault 3110. Because the PoE damper is offline, a duct pressure of a ductthat the PoE damper is connected to may not meet a setpoint.Accordingly, a duct pressure fault 3112 may exist.

In response to generating the nested fault tree 3102, the nested faultengine 3100 can select one or multiple root faults for presentation tothe user device 124. The nested fault engine 3100 can be configured tocommunicate the root fault to the dynamic UX service 120. In someembodiments, the nested fault engine 3100 identifies which nodes of thenested fault tree 3102 do not depend from any other faults, the nestedfault engine 3100 can select these nodes as the root nodes and providethose nodes to the dynamic UX service 120.

Referring now to FIG. 32, a graph data structure 3200 that the dynamicUX service 120 can query for information is shown, the graph datastructure including user roles, according to an exemplary embodiment.The graph data structure 3200 can be an example of the knowledgebase 118or a component of the knowledgebase 118. The graph data structure 3200includes multiple nodes and edges, i.e., nodes 3202-3222 and edges3224-3242. The nodes 3202-3222 represent entities of the building 102,i.e., data, equipment, areas, and the building 102 itself. The edges3224-3242 represent relationships between the various entities of thebuilding 102.

The nodes 3202-3222 include a Joe node 3204. The Joe node 3204represents an individual Joe who is a building owner, represented by anisA edge 3224 between the Joe node 3204 and a building owner node 3202.Another node, Patrick node 3206 represents another individual, Patrick.Patrick may report to Joe, i.e., Joe employs Patrick or is otherwisePatrick's superior. This relationship between Patrick and Joe may berepresented by a reportsTo edge 3226 from the Patrick node 3206 to theJoe node 3204. While Joe may own the building, Patrick may beresponsible for managing the building, i.e., Patrick may be a buildingmanager. This is indicated by an edge isA 3228 between the Patrick node3206 and a building manager node 3208.

Patrick may supervise a building technician for the building, thisbuilding technician may be an individual, Anthony, represented by anAnthony node 3210. The supervision of Anthony by Patrick can berepresented by a manages edge 3230 between the Patrick node 3206 and theAnthony node 3210. The graph data structure 3200 can represent Anthonyas the building technician based on an isA edge 3232 between the Anthonynode 3210 and a building technician node 3212.

The building technician of the building, i.e., Anthony, may haveparticular responsibilities in the building, for example, maintainingand servicing HVAC devices. The HVAC devices of the building may berepresented by an HVAC devices node 3214. Anthony's responsibility forthe HVAC devices may be represented by an isResponsibleFor edge 3234between the building technician node 3212 and the HVAC devices node3214.

The HVAC devices of the building may include room thermostats, VAVs, andan AHU. The room thermostats can be represented by a set of roomthermostat nodes 3220, a set of VAV nodes 3218, and an AHU node 3216.Includes edges 3236, 3240, and 3238 between the HVAC devices node 3214and the set of room thermostat nodes 3220, the set of VAV nodes 3218,and the AHU node 3216.

FIG. 32 further includes the user device 124 and the dynamic UX service120. The dynamic UX service 120 can be configured to generatepresentations for the user device 124 based on the role informationincluded within the graph data structure 3200. For example, someinformation should only be surfaced to an appropriate individual. Forexample, since Patrick manages Anthony, the performance of Anthony,tasks associated with Anthony, etc. can be viewed by Patrick. However,information pertaining to Joe may not be viewable by Patrick sincePatrick reports to Joe.

In some embodiments, the presentation that the dynamic UX service 120generates is initiated by the user device 124 providing the dynamic UXservice 120 with a question. The question may be a question forinformation that is in some way associated with or restricted by rolesindicated by the graph data structure 3200. For example, if the questionis “What tasks does Anthony have to complete?” this may be restrictedbased on who Anthony reports to. Another question, “How much does Joeearn?” may also be restricted based on role. The dynamic UX service 120can query the graph data structure 3200 for both information pertainingto the question received from the user device 124 but also retrievecontextual information indicating how the presentation should begenerated or presentation to the user device 124, i.e., the context maybe nodes or edges of the graph data structure 3200 that indicate rolesof entities of the graph data structure.

For example, the question received by the dynamic UX service 120 may begenerated by Patrick. The question may be “show me tasks that Anthonyneeds to perform.” The dynamic UX service 120 can query the graph datastructure 3200 to identify tasks associated with Anthony, e.g., thefaults linked to the set of room thermostat nodes 3220. The dynamic UXservice 120 can further query the graph data structure 3200 for roleinformation pertaining to Patrick and Anthony. For example, the querycan return the building manager node 3208 or the building techniciannode 3212. Furthermore, the query could return an edge, the manages edge3230 between the Patrick node 3206 and the Anthony node 3210. Based onthe returned role data, the dynamic UX service 120 can compose thepresentation. Since Patrick manages Anthony, the presentation to Patrickmay include all the details of fault data that Anthony needs to handle.However, if another user that does not manage Anthony was to ask thesame question, the Dynamic UX service 120 may provide basic informationregarding Anthony, i.e., that he is a building technician instead ofproviding the tasks that Anthony needs to perform. This dynamiccomposition can control the amount of detail is provided about Anthony.

In some embodiments, information can be proactively pushed to the userdevice 124 based on role information of the graph data structure 3200.For example, if the fault data 3222 indicates a fault that has not beenaddressed for a first predefined period of time, the dynamic UX service120 can determine that Anthony 3210 is responsible for the faults. Thedynamic UX service 120 can determine that Anthony is responsible for thefaults through the relationships of the graph data structure 3200, i.e.the isA edge 3232 between Anthony 3210 and the building technician node3212, the isResponsibleFor edge 3234 between the building techniciannode 3212 and the HVAC devices node 3214, the includes edge 3236 betweenthe HVAC devices node 3214 and the set of room thermostat nodes 3220,and the has edge 3242 between the set of room thermostat nodes 3220 andthe fault data node 3222.

If Anthony does not address the fault with a second predefined amount oftime, the dynamic UX service 120 can escalate the faults, and theperformance of Anthony, to another user. The user that the faults shouldbe escalated to is Patrick and the dynamic UX service 120 can identifyPatrick as the appropriate individual to escalate the faults to based onthe manages edge 3230 between the Patrick node 3206 and the Anthony node3210. The dynamic UX service 120 can compose a presentation indicatingthe faults and Anthony's failure to address the faults and push thepresentation to a user device associated with Patrick.

If the faults are still not addressed after a third predefined amount oftime, the dynamic UX service 120 can escalate the faults, theperformance of Anthony, and the performance of Patrick to another user.The user that the faults should be escalated to is Joe and the dynamicUX service 120 can identify Joe as the appropriate individual toescalate the faults to based on the edge reportsTo 3226 between thePatrick node 3206 and the Joe node 3204. The dynamic UX service 120 cancompose a presentation indicating the faults, Anthony's failure toaddress the faults, and Patrick's failure to address the faults to auser device associated with Joe.

Referring now to FIG. 33, a block diagram of a question frequency graph3300 including information indicating how often users ask particularquestions is shown, according to an exemplary embodiment. The questionfrequency graph 3300 can be an example of the knowledgebase 118 or acomponent of the knowledgebase 118. The graph data structure 3330includes multiple nodes and edges, i.e., nodes 3302-3318 and edges3328-3340. The nodes 3202-3222 represent entities of a building andtypes of questions. The edges 3224-3242 represent relationships betweenthe various entities and the frequency scores indicating how often usersask certain types of question.

The nodes 3302, 3304, 3306, 3316, and 3318 represent different types ofquestions or insights that a user may ask the dynamic UX service 120.The node 3302 may indicate an equipment setpoint recommendationquestion. Questions that pertain to identifying a value for a setpointfor a space or piece of equipment may be associated with the node 3302.Questions that pertain to determining energy savings for a building orpiece of equipment may be associated with the node 3304. Questions thatpertain to determine when spaces of a building will be occupied areassociated with the node 3306. Questions that pertain to reducing thenumber of security alarms that are false that occur within a buildingare associated with the node 3318. Questions that pertain to aggregatinginformation in reports for faults of security devices are associatedwith the node 3316.

The nodes can further include indications of users, i.e., a user Haley,a user Mike, and a user Sarah. Haley may be associated with the Haleynode 3306, Mike may be associated with the Mike node 3310, and Sarah maybe associated with the Sarah node 3312. Furthermore, the nodes mayindicate role nodes. A building owner role can be represented by thebuilding owner node 3308. A security technician role can be representedby the security technician node 3314. Haley and Mike may both bebuilding owners and thus an isA edge 3320 may exist between the Haleynode 3306 and the building owner node 3308 and an isA edge 3322 mayexist between the Mike node 3310 and the security technician node 3314.Sarah may be a security technician and thus an isA edge 3324 may existbetween the Sarah node 3312 and the security technician node 3314.

Frequency score edges 3326-3330, with particular score values may existbetween the Haley node 3306 and the question nodes 3302-3306. Similarly,frequency score edges 3332 and 3334 with particular score values mayexist between the Mike node 3310 and the question nodes 3304 and 3306.Furthermore, frequency score edges 3336-3340 may exist with particularscore values between the Sarah node 3312 and the question nodes 3304,3316, and 3318.

In some embodiments, the dynamic UX service 120 generates and/or updatesthe frequency score edges to include or be values indicating howfrequently a user asks a particular question or how interested a user isin a particular question. For example, the scores may be updated as eachquestion is received by the dynamic UX service 120 from the user device124. For example, the dynamic UX service 120 can identify which questionnode (i.e., what question topic) a particular question falls under andwhat user is asking the question. Based on the identification of theuser, the score between the node representing the user and theidentified question node can be updated to be a new value. In someembodiments, the score indicates a total number of time a user has askeda question. In some embodiments, the score indicates a total number oftimes a user has asked a question in the last predefined period of time(e.g., in the last day, month, year, etc.).

The dynamic UX service 120 can generate presentations for the userdevice that include synthetic insights. The dynamic UX service 120 cangenerate the synthetic insight based on querying a knowledgebase 118 andreceiving data for generating the synthetic insight. The type of datarequired for generating the synthetic insight and the processing forgenerating the synthetic insight can be determined based on thefrequency scores of the query frequency graph 3300.

For example, the dynamic UX service 120 could identify that Mike neverasks questions about equipment setpoints, i.e., no edge exists (or anedge with a low score exists). Since Mike is a building owner, thedynamic UX service 120 can identify what questions other building ownersare asking, i.e., the dynamic UX service 120 can identify that Haley hasa frequency score of “8” for asking the equipment setpoint question. Thedynamic UX service 120 can generate a synthetic insight for equipmentsetpoints and push the synthetic insight to a user device of Mike.

In some embodiments, the dynamic UX service 120 can identify that a userasks a question frequently based on the frequency scores (e.g., afrequency score greater than a predefined amount). For example, Sarahasks questions regarding false alarm reduction frequently, i.e., thefrequency score edge 3340 between the Sarah node 3312 and the falsealarm reduction node 3318 is a “7.” The dynamic UX service 120 candetermine that Sarah is interested in reducing false alarms and canquery the knowledgebase 118 for data and cause false alarm reductionanalytics to be run, even if Sarah does not ask for the analytics to berun. If an insight is identified, the dynamic UX service 120 can pushthe insight to a user device of Sarah.

Configuration of Exemplary Embodiments

The construction and arrangement of the systems and methods as shown inthe various exemplary embodiments are illustrative only. Although only afew embodiments have been described in detail in this disclosure, manymodifications are possible (e.g., variations in sizes, dimensions,structures, shapes and proportions of the various elements, values ofparameters, mounting arrangements, use of materials, colors,orientations, etc.). For example, the position of elements may bereversed or otherwise varied and the nature or number of discreteelements or positions may be altered or varied. Accordingly, all suchmodifications are intended to be included within the scope of thepresent disclosure. The order or sequence of any process or method stepsmay be varied or re-sequenced according to alternative embodiments.Other substitutions, modifications, changes, and omissions may be madein the design, operating conditions and arrangement of the exemplaryembodiments without departing from the scope of the present disclosure.

The present disclosure contemplates methods, systems and programproducts on any machine-readable media for accomplishing variousoperations. The embodiments of the present disclosure may be implementedusing existing computer processors, or by a special purpose computerprocessor for an appropriate system, incorporated for this or anotherpurpose, or by a hardwired system. Embodiments within the scope of thepresent disclosure include program products comprising machine-readablemedia for carrying or having machine-executable instructions or datastructures stored thereon. Such machine-readable media can be anyavailable media that can be accessed by a general purpose or specialpurpose computer or other machine with a processor. By way of example,such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROMor other optical disk storage, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to carry or storedesired program code in the form of machine-executable instructions ordata structures and which can be accessed by a general purpose orspecial purpose computer or other machine with a processor. Wheninformation is transferred or provided over a network or anothercommunications connection (either hardwired, wireless, or a combinationof hardwired or wireless) to a machine, the machine properly views theconnection as a machine-readable medium. Thus, any such connection isproperly termed a machine-readable medium. Combinations of the above arealso included within the scope of machine-readable media.Machine-executable instructions include, for example, instructions anddata which cause a general purpose computer, special purpose computer,or special purpose processing machines to perform a certain function orgroup of functions.

Although the figures show a specific order of method steps, the order ofthe steps may differ from what is depicted. Also two or more steps maybe performed concurrently or with partial concurrence. Such variationwill depend on the software and hardware systems chosen and on designerchoice. All such variations are within the scope of the disclosure.Likewise, software implementations could be accomplished with standardprogramming techniques with rule based logic and other logic toaccomplish the various connection steps, processing steps, comparisonsteps and decision steps.

What is claimed:
 1. A building system comprising one or more storagedevices having instructions stored thereon that, when executed by one ormore processors, cause the one or more processors to: receive anunstructured user question from a user device of a user; query a graphdatabase based on the unstructured user question to extract contextassociated with the unstructured user question from contextualinformation of a building stored by the graph database, wherein thegraph database stores the contextual information of the building througha plurality of nodes and a plurality of edges between the plurality ofnodes, wherein the plurality of nodes represent equipment, spaces,people, and events associated with the building and the plurality ofedges represent relationships between the equipment, spaces, people, andevents, wherein the one or more processors are configured to extract thecontext for multiple portions of the unstructured user question acrosstwo or more of the equipment, spaces, people, or events; retrieve datafrom one or more data sources based on the context to generate aresponse to the user question; and compose a presentation based on theretrieved data.
 2. The building system of claim 1, wherein the one ormore data sources are one or more particular nodes of the graphdatabase.
 3. The building system of claim 1, wherein the instructionscause the one or more processors to implement: a data ingestion serviceconfigured to collect the data from an edge device of the building andingest the data into the graph database; the graph database, wherein thegraph database is configured to store the data; and a dynamic userexperience service configured to receive the unstructured user question,query the graph database, and compose the presentation.
 4. The buildingsystem of claim 1, wherein the unstructured user question is a string;wherein the instructions cause the one or more processors to: decomposethe string to determine a requested information context and apresentation context based on the string; query the graph database forthe data of the building based on the requested information context; andcompose the presentation based on the data and the presentation contextby determining a format of the presentation based on the presentationcontext.
 5. The building system of claim 1, wherein the plurality ofnodes represent the data.
 6. The building system of claim 1, wherein theunstructured user question is a string comprising an identifier of anedge device associated with the data and an indication of a type of thedata; wherein the instructions cause the one or more processors to:decompose the string to determine a first component and a secondcomponent of the string, wherein the first component is the identifierof the edge device associated with the data and the second component isthe type of the data; and query the graph database for the data of thebuilding with the first component and the second component.
 7. Thebuilding system of claim 1, wherein the unstructured user question is astring comprising an indication of a requested output presentation,wherein the requested output presentation is at least one of a visualoutput presentation, a textual output presentation, or an audible outputpresentation; wherein the instructions cause the one or more processorsto: decompose the string to determine a component of the string, whereinthe component is the indication of the requested output presentation;and compose the presentation based on the component of the string by:determining whether the component indicates the visual outputpresentation, the textual output presentation, or the audible outputpresentation; composing the presentation as the visual outputpresentation in response to a first determination that the componentindicates the visual output presentation; composing the presentation asthe text output presentation in response to a second determination thatthe component indicates the text output presentation; and composing thepresentation as the audible output presentation in response to a thirddetermination that the component indicates the audible outputpresentation.
 8. The building system of claim 1, wherein theinstructions cause the one or more processors to: query the graphdatabase for at least a portion of the data and a context portion of thecontextual information describing the building; perform one or moreanalytic algorithms based on the portion of the data and the contextportion of the contextual information to generate one or more analyticsresults; and push the one or more analytics results to the user deviceof the user.
 9. The building system of claim 8, wherein the instructionscause the one or more processors to: retrieve at least one of historicalquestion data associated with the user or user contextual datadescribing the user; and select the one or more analytic algorithms froma plurality of analytic algorithms based on at least one of thehistorical question data associated with the user or the user contextualdata describing the user.
 10. The building system of claim 1, whereinthe unstructured user question is a string; wherein the instructionscause the one or more processors to: decompose the string to determine arequested information context and a presentation context; query thegraph database for the context based on the requested informationcontext; generate a query data structure based on the context; query thegraph database based on the query data structure for the data of thebuilding; and compose the presentation based on the data and thepresentation context.
 11. The building system of claim 10, wherein therequested information context comprises a request for one or moreactions associated with the user of the user device, wherein therequested information context further comprises an indication of theuser.
 12. The building system of claim 10, wherein the context comprisesat least one of one or more particular nodes of the graph database orone or more particular edges of the graph database; wherein theinstructions cause the one or more processors to generate the query datastructure by causing the query data structure to include one or moreparameters based on at least one of the one or more particular nodes ofthe graph database or the one or more particular edges of the graphdatabase.
 13. The building system of claim 1, wherein the instructionscause the one or more processors to: receive an indication of the databeing ingested into the graph database; determine, based on the data,that a presentation rule of a plurality of presentation rules istriggered based on the data; query the graph database based on thepresentation rule and the data to identify the user; compose a secondpresentation based on the data and the presentation rule; and push thesecond presentation to the user device of the user.
 14. The buildingsystem of claim 13, wherein the instructions cause the one or moreprocessors to: retrieve historical question data based on an identity ofthe user; identify one or more presentation preferences of the userbased on the historical question data; and compose the secondpresentation based on the data, the presentation rule, and the one ormore presentation preferences.
 15. The building system of claim 13,wherein the instructions cause the one or more processors to compose thesecond presentation based on the data and the presentation rule by:selecting one presentation template from a plurality of presentationtemplates based on the data and the presentation rule, wherein each ofthe plurality of presentation templates defines a presentation format;and composing the second presentation based on the data and the onepresentation template.
 16. A method comprising: receiving, by aprocessing circuit, an unstructured user question from a user device ofa user; querying, by the processing circuit, a database based on theunstructured user question to extract context associated with theunstructured user question from contextual information of a buildingstored by the database, wherein the database stores the contextualinformation of the building through a plurality of nodes and a pluralityof edges between the plurality of nodes, wherein the plurality of nodesrepresent equipment, spaces, people, and events associated with thebuilding and the plurality of edges represent relationships between theequipment, spaces, people, and events, wherein the querying comprisesextracting the context for multiple portions of the unstructured userquestion across two or more of the equipment, spaces, people, or events;retrieving, by the processing circuit, data from one or more datasources based on the context to generate a response to the userquestion; and composing, by the processing circuit, a presentation basedon the retrieved data.
 17. The method of claim 16, wherein theunstructured user question is a string; wherein the method furthercomprises: decomposing, by the processing circuit, the string todetermine a requested information context and a presentation contextbased on the string; querying, by the processing circuit, the databasefor the data of the building based on the requested information context;and composing, by the processing circuit, the presentation based on thedata and the presentation context by determining a format of thepresentation based on the presentation context.
 18. The method of claim16, wherein the plurality of nodes represent the data.
 19. The method ofclaim 16, wherein the database is a graph database; wherein the one ormore data sources are one or more particular nodes of the graphdatabase.
 20. The method of claim 16, wherein the unstructured userquestion is a string comprising an identifier of an edge deviceassociated with the data and an indication of a type of the data;wherein the method further comprises: decomposing, by the processingcircuit, the string to determine a first component and a secondcomponent of the string, wherein the first component is the identifierof the edge device associated with the data and the second component isthe type of the data; and querying, by the processing circuit, thedatabase for the data of the building with the first component and thesecond component.
 21. The method of claim 16, wherein the unstructureduser question is a string comprising an indication of a requested outputpresentation, wherein the requested output presentation is at least oneof a visual output presentation, a textual output presentation, or anaudible output presentation; wherein the method further comprises:decomposing, by the processing circuit, the string to determine acomponent of the string, wherein the component is the indication of therequested output presentation; and composing, by the processing circuit,the presentation based on the component of the string by: determiningwhether the component indicates the visual output presentation, thetextual output presentation, or the audible output presentation;composing the presentation as the visual output presentation in responseto a first determination that the component indicates the visual outputpresentation; composing the presentation as the text output presentationin response to a second determination that the component indicates thetext output presentation; and composing the presentation as the audibleoutput presentation in response to a third determination that thecomponent indicates the audible output presentation.
 22. The method ofclaim 16, further comprising: querying, by the processing circuit, thedatabase for at least a portion of the data and a context portion of thecontextual information describing the building; performing, by theprocessing circuit, one or more analytic algorithms based on the portionof the data and the context portion of the contextual information togenerate one or more analytics results; and pushing, by the processingcircuit, the one or more analytics results to the user device of theuser.
 23. The method of claim 22, further comprising: retrieving, by theprocessing circuit, at least one of historical question data associatedwith the user or user contextual data describing the user; andselecting, by the processing circuit, the one or more analyticalgorithms from a plurality of analytic algorithms based on at least oneof the historical question data associated with the user or the usercontextual data describing the user.
 24. The method of claim 16, whereinthe unstructured user question is a string; wherein the method furthercomprises: decomposing, by the processing circuit, the string todetermine a requested information context and a presentation context;querying, by the processing circuit, the database for the context basedon the requested information context; generating, by the processingcircuit, a query data structure based on the context; querying, by theprocessing circuit, the database based on the query data structure forthe data of the building; and composing, by the processing circuit, thepresentation based on the data and the presentation context.
 25. Themethod of claim 24, wherein the requested information context comprisesa request for one or more actions associated with the user of the userdevice, wherein the requested information context further comprises anindication of the user.
 26. The method of claim 24, wherein the contextcomprises at least one of one or more particular nodes of the databaseor one or more particular edges of the database; wherein the methodfurther comprises generating, by the processing circuit, the query datastructure by causing the query data structure to include one or moreparameters based on at least one of the one or more particular nodes ofthe database or the one or more particular edges of the database. 27.The method of claim 16, further comprising: receiving, by the processingcircuit, an indication of the data being ingested into the database;determining, by the processing circuit, based on the data, that apresentation rule of a plurality of presentation rules is triggeredbased on the data; querying, by the processing circuit, the databasebased on the presentation rule and the data to identify the user;composing, by the processing circuit, a second presentation based on thedata and the presentation rule; and pushing, by the processing circuit,the second presentation to the user device of the user.
 28. The methodof claim 27, further comprising retrieving, by the processing circuit,historical question data based on an identity of the user; identifying,by the processing circuit, one or more presentation preferences of theuser based on the historical question data; and composing, by theprocessing circuit, the second presentation based on the data, thepresentation rule, and the one or more presentation preferences.
 29. Abuilding management system of a building comprising: one or more storagedevices configured to store instructions and store a knowledgebasecomprising contextual information of the building, wherein thecontextual information comprises representations of equipment, spaces,people, and events associated with the building and relationshipsbetween the equipment, spaces, people, and events; and one or moreprocessing circuits configured to execute the instructions causing theone or more processing circuits to: receive an unstructured userquestion from a user device of a user; query the knowledgebase based onthe unstructured user question to extract context associated with theunstructured user question from the contextual information of thebuilding stored by the knowledgebase, wherein the one or more processorsare configured to extract the context for multiple portions of theunstructured user question across two or more of the equipment, spaces,people, or events; retrieve data from the knowledgebase based on thecontext to generate a response to the user question; and compose apresentation based on the retrieved data.
 30. The building managementsystem of claim 29, wherein the knowledgebase is a digital twin thatprovides a virtual representation of the equipment, spaces, people, andevents associated with the building.